Power Control for Channel State Information

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A base station may send, to a wireless device, one or more radio resource control messages comprising power control parameters and/or other wireless resources. The base station may send, to the wireless device, activation or deactivation of channel state information reporting. The wireless device may adjust, based on one or more of the activation or deactivation, at least one value associated with a transmission power of an uplink channel transmission.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Nos.62/615,909, titled “Power Control Command For SP CSI” and filed on Jan.10, 2018, and 62/616,189, titled “Power Control For SP CSI” and filed onJan. 11, 2018, the disclosures of which are hereby incorporated byreference in their entirety.

BACKGROUND

In wireless communications, wireless devices may have limited resources,such as power required, for example, for various transmissions. A basestation may determine that one or more wireless devices should reportchannel state information which may require additional power totransmit. It is desired to improve wireless communications withoutadversely increasing signaling overhead and/or decreasing spectralefficiency.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for controlling atransmission power of one or more wireless devices. A base station maysend, to a wireless device, one or more radio resource control messagescomprising power control parameters and/or other wireless resources. Thebase station may send, to the wireless device, activation ordeactivation of a channel state information (CSI) report. The wirelessdevice may adjust, based on one or more of the activation ordeactivation, at least one value associated with a transmission power ofan uplink channel transmission. The at least one value may comprise oneor more correction values associated with the transmission power of theuplink channel transmission. At least one of an uplink data channel or asemi-persistent (SP) CSI report may be dropped. A transmission power ofat least one of an uplink data channel or an SP CSI report may beadjusted (e.g., scaled down).

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows example sets of orthogonal frequency division multiplexing(OFDM) subcarriers.

FIG. 2 shows example transmission time and reception time for twocarriers in a carrier group.

FIG. 3 shows example OFDM radio resources.

FIG. 4 shows hardware elements of a base station and a wireless device.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D show examples for uplink anddownlink signal transmission.

FIG. 6 shows an example protocol structure with multi-connectivity.

FIG. 7 shows an example protocol structure with carrier aggregation (CA)and dual connectivity (DC).

FIG. 8 shows example timing advance group (TAG) configurations.

FIG. 9 shows example message flow in a random access process in asecondary TAG.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F showexamples for architectures of tight interworking between a 5G RAN and along term evolution (LTE) radio access network (RAN).

FIG. 12A, FIG. 12B, and FIG. 12C show examples for radio protocolstructures of tight interworking bearers.

FIG. 13A and FIG. 13B show examples for gNodeB (gNB) deployment.

FIG. 14 shows functional split option examples of a centralized gNBdeployment.

FIG. 15 shows an example of one or more downlink control information(DCI) formats.

FIG. 16 shows an example of one or more DCI formats.

FIG. 17 shows an example of channel state information reference signal(CSI-RS) configurations.

FIG. 18 shows example subband sizes.

FIG. 19 shows an example priority order associated with one or more CSIreports.

FIG. 20 shows an example semi-persistent channel state information (SPCSI) configuration with a message activating SP CSI and a messagedeactivating SP CSI.

FIG. 21 shows an example parameter of a TPC command.

FIG. 22 shows an example parameter of a TPC command

FIG. 23 shows an example of using a DCI for activating and deactivatingSP CSI.

FIG. 24A and FIG. 24B show examples of a validation of SP CSI activationor SP CSI deactivation.

FIG. 25A and FIG. 25B show examples of a validation of SP CSI activationor SP CSI deactivation.

FIG. 26 shows an example of adjusting a correction value after receivinga DCI associated with SP CSI.

FIG. 27 shows an example of adjusting a correction value after receivinga media access control control element (MAC CE) associated with SP CSI.

FIG. 28A and FIG. 28B show examples of a window for physical downlinkcontrol channel (PDCCH) monitoring for SP CSI and SP CSI reporttransmission.

FIG. 29 shows an example SP CSI configuration with a message activatingSP CSI and a message deactivating SP CSI.

FIG. 30 shows an example of an SP CSI activation procedure that may beperformed by a base station.

FIG. 31 shows an example of an SP CSI reporting procedure that may beperformed by a wireless device.

FIG. 32A, FIG. 32B and FIG. 32C show examples of a MAC subheader.

FIG. 33A and FIG. 33B show examples of uplink/downlink (UL/DL) MACprotocol data unit (PDU).

FIG. 34A and FIG. 34B show examples of SP CSI piggybacking on PUSCHdata.

FIG. 35A and FIG. 35B show examples of selecting power control parametervalues.

FIG. 36 shows an example of transmit power scaling.

FIG. 37A and FIG. 37B show example power allocations.

FIG. 38 shows an example power allocation based on a power scaling.

FIG. 39A and FIG. 39B show example power allocations.

FIG. 40 shows an example power allocation based on a power scaling.

FIG. 41 shows an example of an uplink grant procedure that may beperformed by a base station.

FIG. 42 shows an example of an uplink power control procedure that maybe performed by a wireless device.

FIG. 43 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings, which form a part hereof, show examples ofthe disclosure. It is to be understood that the examples shown in thedrawings and/or discussed herein are non-exclusive and that there areother examples of how the disclosure may be practiced.

The features described herein may enable operation of carrieraggregation and may be used in the technical field of multicarriercommunication systems. The features described herein may relate to powercontrol in multicarrier communication systems.

The following acronyms are used throughout the present disclosure,provided below for convenience although other acronyms may be introducedin the detailed description:

5G 5th generation wireless systemsASIC application-specific integrated circuitBPSK binary phase shift keyingCA carrier aggregationCC component carrierCDMA code division multiple accessCP cyclic prefixCPLD complex programmable logic devicesCRC cyclic redundancy check bitsCSI channel state informationCSS common search spaceCU central unitDC dual connectivityDCI downlink control informationDL downlinkDU distributed unitEPC evolved packet coreE-UTRAN evolved-universal terrestrial radio access networkFDD frequency division multiplexingFPGA field programmable gate arraysFs-C Fs-control planeFs-U Fs-user planegNB next generation node BHARQ hybrid automatic repeat requestHDL hardware description languagesLTE long term evolutionMAC media access controlMAC-CE media access control-control elementMCG master cell groupMIB master information blockMME mobility management entityNAS non-access stratumNG CP next generation control plane coreNGC next generation coreNG-C NG-control planeNG-U NG-user planeNR MAC new radio MACNR PDCP new radio PDCPNR PHY new radio physicalNR RLC new radio RLCNR RRC new radio RRCNR new radioNSSAI network slice selection assistance informationOFDM orthogonal frequency division multiplexingPCC primary component carrierPCell primary cellPDCCH physical downlink control channelPDCP packet data convergence protocolPDSCH physical downlink shared channelPDU packet data unitPHY physicalPLMN public land mobile networkPSCell primary secondary cellpTAG primary timing advance groupPUCCH physical uplink control channelPUSCH physical uplink shared channelQAM quadrature amplitude modulationQPSK quadrature phase shift keyingRA random accessRB resource blocksRBG resource block groupsRLC radio link controlRRC radio resource controlSCC secondary component carrierSCell secondary cellSCells secondary cellsSCG secondary cell groupSC-OFDM single carrier-OFDMSDU service data unitSFN system frame numberS-GW serving gatewaySIB system information blockSRB signaling radio bearersTAG secondary timing advance groupTA timing advanceTAG timing advance groupTAI tracking area identifierTAT time alignment timerTB transport blockTDD time division duplexingTDMA time division multiple accessTTI transmission time intervalUE user equipmentUL uplinkUPGW user plane gatewayURLLC ultra-reliable low-latency communicationsVHDL VHSIC hardware description languageXn-C Xn-control planeXn-U Xn-user planeXx-C Xx-control planeXx-U Xx-user plane

Examples may be implemented using various physical layer modulation andtransmission mechanisms. Example transmission mechanisms may include,but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/orthe like. Hybrid transmission mechanisms such as TDMA/CDMA, andOFDM/CDMA may also be employed. Various modulation schemes may be usedfor signal transmission in the physical layer. Examples of modulationschemes include, but are not limited to: phase, amplitude, code, acombination of these, and/or the like. An example radio transmissionmethod may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM,and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme depending on transmission requirements and radio conditions.

FIG. 1 shows example sets of OFDM subcarriers. As shown in this example,arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDMsystem. The OFDM system may use technology such as OFDM technology,DFTS-OFDM, SC-OFDM technology, or the like. For example, arrow 101 showsa subcarrier transmitting information symbols. FIG. 1 is shown as anexample, and a typical multicarrier OFDM system may include moresubcarriers in a carrier. For example, the number of subcarriers in acarrier may be in the range of 10 to 10,000 subcarriers. FIG. 1 showstwo guard bands 106 and 107 in a transmission band. As shown in FIG. 1,guard band 106 is between subcarriers 103 and subcarriers 104. Theexample set of subcarriers A 102 includes subcarriers 103 andsubcarriers 104. FIG. 1 also shows an example set of subcarriers B 105.As shown, there is no guard band between any two subcarriers in theexample set of subcarriers B 105. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarrier.

FIG. 2 shows an example timing arrangement with transmission time andreception time for two carriers. A multicarrier OFDM communicationsystem may include one or more carriers, for example, ranging from 1 to10 carriers. Carrier A 204 and carrier B 205 may have the same ordifferent timing structures. Although FIG. 2 shows two synchronizedcarriers, carrier A 204 and carrier B 205 may or may not be synchronizedwith each other. Different radio frame structures may be supported forFDD and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing.Downlink and uplink transmissions may be organized into radio frames201. In this example, radio frame duration is 10 milliseconds (msec).Other frame durations, for example, in the range of 1 to 100 msec mayalso be supported. Each 10 msec radio frame 201 may be divided into tenequally sized subframes 202. Other subframe durations such as including0.5 msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s)may comprise two or more slots (e.g., slots 206 and 207). For theexample of FDD, 10 subframes may be available for downlink transmissionand 10 subframes may be available for uplink transmissions in each 10msec interval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may include all downlink, all uplink, or a downlink part andan uplink part, and/or alike. Slot aggregation may be supported, forexample, data transmission may be scheduled to span one or multipleslots. For example, a mini-slot may start at an OFDM symbol in asubframe. A mini-slot may have a duration of one or more OFDM symbols.Slot(s) may include a plurality of OFDM symbols 203. The number of OFDMsymbols 203 in a slot 206 may depend on the cyclic prefix length andsubcarrier spacing.

FIG. 3 shows an example of OFDM radio resources. The resource gridstructure in time 304 and frequency 305 is shown in FIG. 3. The quantityof downlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g., 301).Resource elements may be grouped into resource blocks (e.g., 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g., 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. A resource block may correspond to one slot in the timedomain and 180 kHz in the frequency domain (for 15 kHz subcarrierbandwidth and 12 subcarriers).

Multiple numerologies may be supported. A numerology may be derived byscaling a basic subcarrier spacing by an integer N. Scalable numerologymay allow at least from 15 kHz to 480 kHz subcarrier spacing. Thenumerology with 15 kHz and scaled numerology with different subcarrierspacing with the same CP overhead may align at a symbol boundary every 1msec in a NR carrier.

FIG. 4 shows hardware elements of a base station 401 and a wirelessdevice 406. A communication network 400 may include at least one basestation 401 and at least one wireless device 406. The base station 401may include at least one communication interface 402, one or moreprocessors 403, and at least one set of program code instructions 405stored in non-transitory memory 404 and executable by the one or moreprocessors 403. The wireless device 406 may include at least onecommunication interface 407, one or more processors 408, and at leastone set of program code instructions 410 stored in non-transitory memory409 and executable by the one or more processors 408. A communicationinterface 402 in the base station 401 may be configured to engage incommunication with a communication interface 407 in the wireless device406, such as via a communication path that includes at least onewireless link 411. The wireless link 411 may be a bi-directional link.The communication interface 407 in the wireless device 406 may also beconfigured to engage in communication with the communication interface402 in the base station 401. The base station 401 and the wirelessdevice 406 may be configured to send and receive data over the wirelesslink 411 using multiple frequency carriers. Base stations, wirelessdevices, and other communication devices may include structure andoperations of transceiver(s). Transceivers, which may comprise both atransmitter and receiver, may be employed in devices such as wirelessdevices, base stations, relay nodes, and/or the like. Examples for radiotechnology implemented in the communication interfaces 402, 407 and thewireless link 411 are shown in FIG. 1, FIG. 2, FIG. 3, FIG. 5, andassociated text. The communication network 400 may comprise any numberand/or type of devices, such as, for example, computing devices,wireless devices, mobile devices, handsets, tablets, laptops, internetof things (IoT) devices, hotspots, cellular repeaters, computingdevices, and/or, more generally, user equipment (e.g., UE). Although oneor more of the above types of devices may be referenced herein (e.g.,UE, wireless device, computing device, etc.), it should be understoodthat any device herein may comprise any one or more of the above typesof devices or similar devices. The communication network 400, and anyother network referenced herein, may comprise an LTE network, a 5Gnetwork, or any other network for wireless communications. Apparatuses,systems, and/or methods described herein may generally be described asimplemented on one or more devices (e.g., wireless device, base station,eNB, gNB, computing device, etc.), in one or more networks, but it willbe understood that one or more features and steps may be implemented onany device and/or in any network. As used throughout, the term “basestation” may comprise one or more of: a base station, a node, a Node B,a gNB, an eNB, an ng-eNB, a relay node (e.g., an integrated access andbackhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB,etc.), an access point (e.g., a WiFi access point), a computing device,a device capable of wirelessly communicating, or any other devicecapable of sending and/or receiving signals. As used throughout, theterm “wireless device” may comprise one or more of: a UE, a handset, amobile device, a computing device, a node, a device capable ofwirelessly communicating, or any other device capable of sending and/orreceiving signals. Any reference to one or more of these terms/devicesalso considers use of any other term/device mentioned above.

The communications network 400 may comprise Radio Access Network (RAN)architecture. The RAN architecture may comprise one or more RAN nodesthat may be a next generation Node B (gNB) (e.g., 401) providing NewRadio (NR) user plane and control plane protocol terminations towards afirst wireless device (e.g. 406). A RAN node may be a next generationevolved Node B (ng-eNB), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device. The first wireless device may communicate with agNB over a Uu interface. The second wireless device may communicate witha ng-eNB over a Uu interface. Base station 401 may comprise one or moreof a gNB, ng-eNB, and/or the like.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of wirelessdevices in RRC_INACTIVE state, distribution function for Non-AccessStratum (NAS) messages, RAN sharing, and dual connectivity or tightinterworking between NR and E-UTRA.

One or more gNBs and/or one or more ng-eNBs may be interconnected witheach other by means of Xn interface. A gNB or an ng-eNB may be connectedby means of NG interfaces to 5G Core Network (5GC). 5GC may comprise oneor more AMF/User Plane Function (UPF) functions. A gNB or an ng-eNB maybe connected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g., non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (e.g., NG-C) interface. The NG-C interface may provide functionssuch as NG interface management, UE context management, UE mobilitymanagement, transport of NAS messages, paging, PDU session management,configuration transfer or warning message transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (if applicable), external PDU sessionpoint of interconnect to data network, packet routing and forwarding,packet inspection and user plane part of policy rule enforcement,traffic usage reporting, uplink classifier to support routing trafficflows to a data network, branching point to support multi-homed PDUsession, QoS handling for user plane, for example, packet filtering,gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink trafficverification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling for mobility between 3^(rd) GenerationPartnership Project (3GPP) access networks, idle mode UE reachability(e.g., control and execution of paging retransmission), registrationarea management, support of intra-system and inter-system mobility,access authentication, access authorization including check of roamingrights, mobility management control (subscription and policies), supportof network slicing and/or Session Management Function (SMF) selection

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or a non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ora non-operational state. The hardware, software, firmware, registers,memory values, and/or the like may be “configured” within a device,whether the device is in an operational or a nonoperational state, toprovide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or a non-operationalstate.

A network (e.g., a 5G network) may include a multitude of base stations,providing a user plane NR PDCP/NR RLC/NR MAC/NR PHY and control plane(e.g., NR RRC) protocol terminations towards the wireless device. Thebase station(s) may be interconnected with other base station(s) (e.g.,employing an Xn interface). The base stations may also be connectedemploying, for example, an NG interface to an NGC. FIG. 10A and FIG. 10Bshow examples for interfaces between a 5G core network (e.g., NGC) andbase stations (e.g., gNB and eLTE eNB). For example, the base stationsmay be interconnected to the NGC control plane (e.g., NG CP) employingthe NG-C interface and to the NGC user plane (e.g., UPGW) employing theNG-U interface. The NG interface may support a many-to-many relationbetween 5G core networks and base stations.

A base station may include many sectors, for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g., TAI), and atRRC connection re-establishment/handover, one serving cell may providethe security input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC); in the uplink, thecarrier corresponding to the PCell may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC); in the uplink,the carrier corresponding to an SCell may be an Uplink SecondaryComponent Carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context in which it is used). The cell ID may beequally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, reference to a firstphysical cell ID for a first downlink carrier may indicate that thefirst physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.Reference to a first carrier that is activated may equally mean that thecell comprising the first carrier is activated.

A device may be configured to operate as needed by freely combining anyof the example features described herein. The disclosed mechanisms maybe performed if certain criteria are met, for example, in a wirelessdevice, a base station, a radio environment, a network, a combination ofthe above, and/or the like. Example criteria may be based, at least inpart, on for example, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like. Ifthe one or more criteria are met, various example embodiments may besatisfied. Therefore, it may be possible to implement examples thatselectively implement disclosed protocols.

A base station may communicate with a variety of wireless devices.Wireless devices may support multiple technologies, and/or multiplereleases of the same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. Referenceto a base station communicating with a plurality of wireless devices mayindicate that a base station may communicate with a subset of the totalwireless devices in a coverage area. A plurality of wireless devices ofa given LTE or 5G release, with a given capability and in a given sectorof the base station, may be used. The plurality of wireless devices mayrefer to a selected plurality of wireless devices, and/or a subset oftotal wireless devices in a coverage area which perform according todisclosed methods, and/or the like. There may be a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices perform based onolder releases of LTE or 5G technology.

A base station may transmit (e.g., to a wireless device) one or moremessages (e.g. RRC messages) that may comprise a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). The other SImay be transmitted via SystemInformationBlockType2. For a wirelessdevice in an RRC_Connected state, dedicated RRC signaling may beemployed for the request and delivery of the other SI. For the wirelessdevice in the RRC_Idle state and/or the RRC_Inactive state, the requestmay trigger a random-access procedure.

A wireless device may send its radio access capability information whichmay be static. A base station may request what capabilities for awireless device to report based on band information. If allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

If CA is configured, a wireless device may have an RRC connection with anetwork. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. If adding a new SCell, dedicatedRRC signaling may be employed to send all required system information ofthe SCell. In connected mode, wireless devices may not need to acquirebroadcasted system information directly from the SCells.

An RRC connection reconfiguration procedure may be used to modify an RRCconnection, (e.g. to establish, modify and/or release RBs, to performhandover, to setup, modify, and/or release measurements, to add, modify,and/or release SCells and cell groups). As part of the RRC connectionreconfiguration procedure, NAS dedicated information may be transferredfrom the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be used to establish (or reestablish, resume) an RRC connection. AnRRC connection establishment procedure may comprise SRB1 establishment.The RRC connection establishment procedure may be used to transfer theinitial NAS dedicated information message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure, for example, after successful securityactivation. A measurement report message may be employed to transmitmeasurement results.

FIG. 5A, FIG. 5B, FIG. 5C, and FIG. 5D show examples of architecture foruplink and downlink signal transmission. FIG. 5A shows an example for anuplink physical channel. The baseband signal representing the physicaluplink shared channel may perform the following processes, which may beperformed by the structures described below. These structures andcorresponding functions are shown as examples, and it is anticipatedthat other mechanisms may be implemented in various examples. Thestructures and corresponding functions may comprise, for example, one ormore scrambling devices 501A and 501B configured to perform scramblingof coded bits in each of the codewords to be transmitted on a physicalchannel; one or more modulation mappers 502A and 502B configured toperform modulation of scrambled bits to generate complex-valued symbols;a layer mapper 503 configured to perform mapping of the complex-valuedmodulation symbols onto one or several transmission layers; one or moretransform precoders 504A and 504B to generate complex-valued symbols; aprecoding device 505 configured to perform precoding of thecomplex-valued symbols; one or more resource element mappers 506A and506B configured to perform mapping of precoded complex-valued symbols toresource elements; one or more signal generators 507A and 507Bconfigured to perform the generation of a complex-valued time-domainDFTS-OFDM/SC-FDMA signal for each antenna port; and/or the like.

FIG. 5B shows an example for performing modulation and up-conversion tothe carrier frequency of the complex-valued DFTS-OFDM/SC-FDMA basebandsignal, for example, for each antenna port and/or for the complex-valuedphysical random access channel (PRACH) baseband signal. For example, thebaseband signal, represented as s₁(t), may be split, by a signalsplitter 510, into real and imaginary components, Re{s₁(t)} andIm{s₁(t)}, respectively. The real component may be modulated by amodulator 511A, and the imaginary component may be modulated by amodulator 511B. The output signal of the modulator 511A and the outputsignal of the modulator 511B may be mixed by a mixer 512. The outputsignal of the mixer 512 may be input to a filtering device 513, andfiltering may be employed by the filtering device 513 prior totransmission.

FIG. 5C shows an example structure for downlink transmissions. Thebaseband signal representing a downlink physical channel may perform thefollowing processes, which may be performed by structures describedbelow. These structures and corresponding functions are shown asexamples, and it is anticipated that other mechanisms may be implementedin various examples. The structures and corresponding functions maycomprise, for example, one or more scrambling devices 531A and 531Bconfigured to perform scrambling of coded bits in each of the codewordsto be transmitted on a physical channel; one or more modulation mappers532A and 532B configured to perform modulation of scrambled bits togenerate complex-valued modulation symbols; a layer mapper 533configured to perform mapping of the complex-valued modulation symbolsonto one or several transmission layers; a precoding device 534configured to perform precoding of the complex-valued modulation symbolson each layer for transmission on the antenna ports; one or moreresource element mappers 535A and 535B configured to perform mapping ofcomplex-valued modulation symbols for each antenna port to resourceelements; one or more OFDM signal generators 536A and 536B configured toperform the generation of complex-valued time-domain OFDM signal foreach antenna port; and/or the like.

FIG. 5D shows an example structure for modulation and up-conversion tothe carrier frequency of the complex-valued OFDM baseband signal foreach antenna port. For example, the baseband signal, represented as s₁^((p))(t), may be split, by a signal splitter 520, into real andimaginary components, Re{s₁ ^((p))(t)} and Im{s₁ ^((p))(t)},respectively. The real component may be modulated by a modulator 521A,and the imaginary component may be modulated by a modulator 521B. Theoutput signal of the modulator 521A and the output signal of themodulator 521B may be mixed by a mixer 522. The output signal of themixer 522 may be input to a filtering device 523, and filtering may beemployed by the filtering device 523 prior to transmission.

FIG. 6 and FIG. 7 show examples for protocol structures with CA andmulti-connectivity. NR may support multi-connectivity operation, wherebya multiple receiver/transmitter (RX/TX) wireless device in RRC_CONNECTEDmay be configured to utilize radio resources provided by multipleschedulers located in multiple gNBs connected via a non-ideal or idealbackhaul over the Xn interface. gNBs involved in multi-connectivity fora certain wireless device may assume two different roles: a gNB mayeither act as a master gNB (e.g., 600) or as a secondary gNB (e.g., 610or 620). In multi-connectivity, a wireless device may be connected toone master gNB (e.g., 600) and one or more secondary gNBs (e.g., 610and/or 620). Any one or more of the Master gNB 600 and/or the secondarygNBs 610 and 620 may be a Next Generation (NG) NodeB. The master gNB 600may comprise protocol layers NR MAC 601, NR RLC 602 and 603, and NR PDCP604 and 605. The secondary gNB may comprise protocol layers NR MAC 611,NR RLC 612 and 613, and NR PDCP 614. The secondary gNB may compriseprotocol layers NR MAC 621, NR RLC 622 and 623, and NR PDCP 624. Themaster gNB 600 may communicate via an interface 606 and/or via aninterface 607, the secondary gNB 610 may communicate via an interface615, and the secondary gNB 620 may communicate via an interface 625. Themaster gNB 600 may also communicate with the secondary gNB 610 and thesecondary gNB 621 via interfaces 608 and 609, respectively, which mayinclude Xn interfaces. For example, the master gNB 600 may communicatevia the interface 608, at layer NR PDCP 605, and with the secondary gNB610 at layer NR RLC 612. The master gNB 600 may communicate via theinterface 609, at layer NR PDCP 605, and with the secondary gNB 620 atlayer NR RLC 622.

FIG. 7 shows an example structure for the UE side MAC entities, forexample, if a Master Cell Group (MCG) and a Secondary Cell Group (SCG)are configured. Media Broadcast Multicast Service (MBMS) reception maybe included but is not shown in this figure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is set up. As an example, threealternatives may exist, an MCG bearer, an SCG bearer, and a splitbearer, such as shown in FIG. 6. NR RRC may be located in a master gNBand SRBs may be configured as a MCG bearer type and may use the radioresources of the master gNB. Multi-connectivity may have at least onebearer configured to use radio resources provided by the secondary gNB.Multi-connectivity may or may not be configured or implemented.

For multi-connectivity, the wireless device may be configured withmultiple NR MAC entities: e.g., one NR MAC entity for a master gNB, andother NR MAC entities for secondary gNBs. In multi-connectivity, theconfigured set of serving cells for a wireless device may comprise twosubsets: e.g., the Master Cell Group (MCG) including the serving cellsof the master gNB, and the Secondary Cell Groups (SCGs) including theserving cells of the secondary gNBs.

At least one cell in a SCG may have a configured UL component carrier(CC) and one of the UL CCs, for example, named PSCell (or PCell of SCG,or sometimes called PCell), may be configured with PUCCH resources. Ifthe SCG is configured, there may be at least one SCG bearer or one splitbearer. If a physical layer problem or a random access problem on aPSCell occurs or is detected, if the maximum number of NR RLCretransmissions has been reached associated with the SCG, or if anaccess problem on a PSCell during a SCG addition or a SCG change occursor is detected, then an RRC connection re-establishment procedure maynot be triggered, UL transmissions towards cells of the SCG may bestopped, a master gNB may be informed by the wireless device of a SCGfailure type, and for a split bearer the DL data transfer over themaster gNB may be maintained. The NR RLC Acknowledge Mode (AM) bearermay be configured for the split bearer. Like the PCell, a PSCell may notbe de-activated. The PSCell may be changed with an SCG change (e.g.,with a security key change and a RACH procedure). A direct bearer typemay change between a split bearer and an SCG bearer, or a simultaneousconfiguration of an SCG and a split bearer may or may not be supported.

A master gNB and secondary gNBs may interact for multi-connectivity. Themaster gNB may maintain the RRM measurement configuration of thewireless device, and the master gNB may, (e.g., based on receivedmeasurement reports, and/or based on traffic conditions and/or bearertypes), decide to ask a secondary gNB to provide additional resources(e.g., serving cells) for a wireless device. If a request from themaster gNB is received, a secondary gNB may create a container that mayresult in the configuration of additional serving cells for the wirelessdevice (or the secondary gNB decide that it has no resource available todo so). For wireless device capability coordination, the master gNB mayprovide some or all of the Active Set (AS) configuration and thewireless device capabilities to the secondary gNB. The master gNB andthe secondary gNB may exchange information about a wireless deviceconfiguration, such as by employing NR RRC containers (e.g., inter-nodemessages) carried in Xn messages. The secondary gNB may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary gNB). The secondary gNB may decide which cell is the PSCellwithin the SCG. The master gNB may or may not change the content of theNR RRC configuration provided by the secondary gNB. In an SCG additionand an SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s). Both a master gNB and asecondary gNBs may know the system frame number (SFN) and subframeoffset of each other by operations, administration, and maintenance(OAM) (e.g., for the purpose of discontinuous reception (DRX) alignmentand identification of a measurement gap). If adding a new SCG SCell,dedicated NR RRC signaling may be used for sending required systeminformation of the cell for CA, except, for example, for the SFNacquired from an MIB of the PSCell of an SCG.

FIG. 7 shows an example of dual-connectivity (DC) for two MAC entitiesat a wireless device side. A first MAC entity may comprise a lower layerof an MCG 700, an upper layer of an MCG 718, and one or moreintermediate layers of an MCG 719. The lower layer of the MCG 700 maycomprise, for example, a paging channel (PCH) 701, a broadcast channel(BCH) 702, a downlink shared channel (DL-SCH) 703, an uplink sharedchannel (UL-SCH) 704, and a random access channel (RACH) 705. The one ormore intermediate layers of the MCG 719 may comprise, for example, oneor more hybrid automatic repeat request (HARQ) processes 706, one ormore random access control processes 707, multiplexing and/orde-multiplexing processes 709, logical channel prioritization on theuplink processes 710, and a control processes 708 providing control forthe above processes in the one or more intermediate layers of the MCG719. The upper layer of the MCG 718 may comprise, for example, a pagingcontrol channel (PCCH) 711, a broadcast control channel (BCCH) 712, acommon control channel (CCCH) 713, a dedicated control channel (DCCH)714, a dedicated traffic channel (DTCH) 715, and a MAC control 716.

A second MAC entity may comprise a lower layer of an SCG 720, an upperlayer of an SCG 738, and one or more intermediate layers of an SCG 739.The lower layer of the SCG 720 may comprise, for example, a BCH 722, aDL-SCH 723, an UL-SCH 724, and a RACH 725. The one or more intermediatelayers of the SCG 739 may comprise, for example, one or more HARQprocesses 726, one or more random access control processes 727,multiplexing and/or de-multiplexing processes 729, logical channelprioritization on the uplink processes 730, and a control processes 728providing control for the above processes in the one or moreintermediate layers of the SCG 739. The upper layer of the SCG 738 maycomprise, for example, a BCCH 732, a DCCH 714, a DTCH 735, and a MACcontrol 736.

Serving cells may be grouped in a TA group (TAG). Serving cells in oneTAG may use the same timing reference. For a given TAG, a wirelessdevice may use at least one downlink carrier as a timing reference. Fora given TAG, a wireless device may synchronize uplink subframe and frametransmission timing of uplink carriers belonging to the same TAG.Serving cells having an uplink to which the same TA applies maycorrespond to serving cells hosted by the same receiver. A wirelessdevice supporting multiple TAs may support two or more TA groups. One TAgroup may include the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not include thePCell and may be called a secondary TAG (sTAG). Carriers within the sameTA group may use the same TA value and/or the same timing reference. IfDC is configured, cells belonging to a cell group (e.g., MCG or SCG) maybe grouped into multiple TAGs including a pTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations. In Example 1, a pTAG comprisesa PCell, and an sTAG comprises an SCell1. In Example 2, a pTAG comprisesa PCell and an SCell1, and an sTAG comprises an SCell2 and an SCell3. InExample 3, a pTAG comprises a PCell and an SCell1, and an sTAG1comprises an SCell2 and an SCell3, and an sTAG2 comprises a SCell4. Upto four TAGs may be supported in a cell group (MCG or SCG), and otherexample TAG configurations may also be provided. In various examples,structures and operations are described for use with a pTAG and an sTAG.Some of the examples may be used for configurations with multiple sTAGs.

An eNB may initiate an RA procedure, via a PDCCH order, for an activatedSCell. The PDCCH order may be sent on a scheduling cell of this SCell.If cross carrier scheduling is configured for a cell, the schedulingcell may be different than the cell that is employed for preambletransmission, and the PDCCH order may include an SCell index. At least anon-contention based RA procedure may be supported for SCell(s) assignedto sTAG(s).

FIG. 9 shows an example of random access processes, and a correspondingmessage flow, in a secondary TAG. A base station, such as an eNB, maytransmit an activation command 900 to a wireless device, such as a UE.The activation command 900 may be transmitted to activate an SCell. Thebase station may also transmit a PDDCH order 901 to the wireless device,which may be transmitted, for example, after the activation command 900.The wireless device may begin to perform a RACH process for the SCell,which may be initiated, for example, after receiving the PDDCH order901. A wireless device may transmit to the base station (e.g., as partof a RACH process) a preamble 902 (e.g., Msg1), such as a random accesspreamble (RAP). The preamble 902 may be transmitted after or in responseto the PDCCH order 901. The wireless device may transmit the preamble902 via an SCell belonging to an sTAG. Preamble transmission for SCellsmay be controlled by a network using PDCCH format 1A. The base stationmay send a random access response (RAR) 903 (e.g., Msg2 message) to thewireless device. The RAR 903 may be after or in response to the preamble902 transmission via the SCell. The RAR 903 may be addressed to a randomaccess radio network temporary identifier (RA-RNTI) in a PCell commonsearch space (CSS). If the wireless device receives the RAR 903, theRACH process may conclude. The RACH process may conclude, for example,after or in response to the wireless device receiving the RAR 903 fromthe base station. After the RACH process, the wireless device maytransmit an uplink transmission 904. The uplink transmission 904 maycomprise uplink packets transmitted via the same SCell used for thepreamble 902 transmission.

Timing alignment (e.g., initial timing alignment) for communicationsbetween the wireless device and the base station may be performedthrough a random access procedure, such as described above regardingFIG. 9. The random access procedure may involve a wireless device, suchas a UE, transmitting a random access preamble and a base station, suchas an eNB, responding with an initial TA command NTA (amount of timingadvance) within a random access response window. The start of the randomaccess preamble may be aligned with the start of a corresponding uplinksubframe at the wireless device assuming NTA=0. The eNB may estimate theuplink timing from the random access preamble transmitted by thewireless device. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The wireless device may determine the initial uplinktransmission timing relative to the corresponding downlink of the sTAGon which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. If an eNB performs anSCell addition configuration, the related TAG configuration may beconfigured for the SCell. An eNB may modify the TAG configuration of anSCell by removing (e.g., releasing) the SCell and adding (e.g.,configuring) a new SCell (with the same physical cell ID and frequency)with an updated TAG ID. The new SCell with the updated TAG ID mayinitially be inactive subsequent to being assigned the updated TAG ID.The eNB may activate the updated new SCell and start scheduling packetson the activated SCell. In some examples, it may not be possible tochange the TAG associated with an SCell, but rather, the SCell may needto be removed and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, such as at least one RRC reconfiguration message,may be sent to the wireless device. The at least one RRC message may besent to the wireless device to reconfigure TAG configurations, forexample, by releasing the SCell and configuring the SCell as a part ofthe pTAG. If, for example, an SCell is added or configured without a TAGindex, the SCell may be explicitly assigned to the pTAG. The PCell maynot change its TA group and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify and/or releaseRBs, to perform handover, to setup, modify, and/or release measurements,to add, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the wirelessdevice may perform an SCell release. If the received RRC ConnectionReconfiguration message includes the sCellToAddModList, the wirelessdevice may perform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH transmission is onlytransmitted on a PCell (e.g., a PSCell) to an eNB. In LTE-Release 12 andearlier, a wireless device may transmit PUCCH information on one cell(e.g., a PCell or a PSCell) to a given eNB. As the number of CA capablewireless devices increases, and as the number of aggregated carriersincrease, the number of PUCCHs and the PUCCH payload size may increase.Accommodating the PUCCH transmissions on the PCell may lead to a highPUCCH load on the PCell. A PUCCH on an SCell may be used to offload thePUCCH resource from the PCell. More than one PUCCH may be configured.For example, a PUCCH on a PCell may be configured and another PUCCH onan SCell may be configured. One, two, or more cells may be configuredwith PUCCH resources for transmitting CSI, acknowledgment (ACK), and/ornon-acknowledgment (NACK) to a base station. Cells may be grouped intomultiple PUCCH groups, and one or more cell within a group may beconfigured with a PUCCH. One SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

A MAC entity may have a configurable timer, for example,timeAlignmentTimer, per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the serving cells belonging tothe associated TAG to be uplink time aligned. If a Timing AdvanceCommand MAC control element is received, the MAC entity may apply theTiming Advance Command for the indicated TAG; and/or the MAC entity maystart or restart the timeAlignmentTimer associated with a TAG that maybe indicated by the Timing Advance Command MAC control element. If aTiming Advance Command is received in a Random Access Response messagefor a serving cell belonging to a TAG, the MAC entity may apply theTiming Advance Command for this TAG and/or start or restart thetimeAlignmentTimer associated with this TAG. Additionally oralternatively, if the Random Access Preamble is not selected by the MACentity, the MAC entity may apply the Timing Advance Command for this TAGand/or start or restart the timeAlignmentTimer associated with this TAG.If the timeAlignmentTimer associated with this TAG is not running, theTiming Advance Command for this TAG may be applied, and thetimeAlignmentTimer associated with this TAG may be started. If thecontention resolution is not successful, a timeAlignmentTimer associatedwith this TAG may be stopped. If the contention resolution issuccessful, the MAC entity may ignore the received Timing AdvanceCommand. The MAC entity may determine whether the contention resolutionis successful or whether the contention resolution is not successful.

A timer may be considered to be running after it is started, until it isstopped, or until it expires; otherwise it may be considered to not berunning. A timer can be started if it is not running or restarted if itis running. For example, a timer may be started or restarted from itsinitial value.

Features described herein may enable operation of multi-carriercommunications. Features may comprise a non-transitory tangible computerreadable media comprising instructions executable by one or moreprocessors to cause operation of multi-carrier communications. Thefeatures may comprise an article of manufacture that comprises anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a device (e.g. wireless communicator, UE, base station, etc.)to enable operation of multi-carrier communications. The devices hereinmay include processors, memory, interfaces, and/or the like. Featuresmay comprise communication networks comprising devices such as basestations, wireless devices (or user equipment: UE), servers, switches,antennas, and/or the like.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork (e.g., NGC) and base stations (e.g., gNB and eLTE eNB). A basestation, such as a gNB 1020, may be interconnected to an NGC 1010control plane employing an NG-C interface. The base station, forexample, the gNB 1020, may also be interconnected to an NGC 1010 userplane (e.g., UPGW) employing an NG-U interface. As another example, abase station, such as an eLTE eNB 1040, may be interconnected to an NGC1030 control plane employing an NG-C interface. The base station, forexample, the eLTE eNB 1040, may also be interconnected to an NGC 1030user plane (e.g., UPGW) employing an NG-U interface. An NG interface maysupport a many-to-many relation between 5G core networks and basestations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexamples for architectures of tight interworking between a 5G RAN and anLTE RAN. The tight interworking may enable a multiplereceiver/transmitter (RX/TX) wireless device in an RRC_CONNECTED stateto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g., an eLTE eNB and a gNB). The two basestations may be connected via a non-ideal or ideal backhaul over the Xxinterface between an LTE eNB and a gNB, or over the Xn interface betweenan eLTE eNB and a gNB. Base stations involved in tight interworking fora certain wireless device may assume different roles. For example, abase station may act as a master base station or a base station may actas a secondary base station. In tight interworking, a wireless devicemay be connected to both a master base station and a secondary basestation. Mechanisms implemented in tight interworking may be extended tocover more than two base stations.

A master base station may be an LTE eNB 1102A or an LTE eNB 1102B, whichmay be connected to EPC nodes 1101A or 1101B, respectively. Thisconnection to EPC nodes may be, for example, to an MME via the S1-Cinterface and/or to an S-GW via the S1-U interface. A secondary basestation may be a gNB 1103A or a gNB 1103B, either or both of which maybe a non-standalone node having a control plane connection via an Xx-Cinterface to an LTE eNB (e.g., the LTE eNB 1102A or the LTE eNB 1102B).In the tight interworking architecture of FIG. 11A, a user plane for agNB (e.g., the gNB 1103A) may be connected to an S-GW (e.g., the EPC1101A) through an LTE eNB (e.g., the LTE eNB 1102A), via an Xx-Uinterface between the LTE eNB and the gNB, and via an S1-U interfacebetween the LTE eNB and the S-GW. In the architecture of FIG. 11B, auser plane for a gNB (e.g., the gNB 1103B) may be connected directly toan S-GW (e.g., the EPC 1101B) via an S1-U interface between the gNB andthe S-GW.

A master base station may be a gNB 1103C or a gNB 1103D, which may beconnected to NGC nodes 1101C or 1101D, respectively. This connection toNGC nodes may be, for example, to a control plane core node via the NG-Cinterface and/or to a user plane core node via the NG-U interface. Asecondary base station may be an eLTE eNB 1102C or an eLTE eNB 1102D,either or both of which may be a non-standalone node having a controlplane connection via an Xn-C interface to a gNB (e.g., the gNB 1103C orthe gNB 1103D). In the tight interworking architecture of FIG. 11C, auser plane for an eLTE eNB (e.g., the eLTE eNB 1102C) may be connectedto a user plane core node (e.g., the NGC 1101C) through a gNB (e.g., thegNB 1103C), via an Xn-U interface between the eLTE eNB and the gNB, andvia an NG-U interface between the gNB and the user plane core node. Inthe architecture of FIG. 11D, a user plane for an eLTE eNB (e.g., theeLTE eNB 1102D) may be connected directly to a user plane core node(e.g., the NGC 1101D) via an NG-U interface between the eLTE eNB and theuser plane core node.

A master base station may be an eLTE eNB 1102E or an eLTE eNB 1102F,which may be connected to NGC nodes 1101E or 1101F, respectively. Thisconnection to NGC nodes may be, for example, to a control plane corenode via the NG-C interface and/or to a user plane core node via theNG-U interface. A secondary base station may be a gNB 1103E or a gNB1103F, either or both of which may be a non-standalone node having acontrol plane connection via an Xn-C interface to an eLTE eNB (e.g., theeLTE eNB 1102E or the eLTE eNB 1102F). In the tight interworkingarchitecture of FIG. 11E, a user plane for a gNB (e.g., the gNB 1103E)may be connected to a user plane core node (e.g., the NGC 1101E) throughan eLTE eNB (e.g., the eLTE eNB 1102E), via an Xn-U interface betweenthe eLTE eNB and the gNB, and via an NG-U interface between the eLTE eNBand the user plane core node. In the architecture of FIG. 11F, a userplane for a gNB (e.g., the gNB 1103F) may be connected directly to auser plane core node (e.g., the NGC 1101F) via an NG-U interface betweenthe gNB and the user plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are examples for radio protocolstructures of tight interworking bearers.

An LTE eNB 1201A may be an S1 master base station, and a gNB 1210A maybe an S1 secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The LTE eNB1201A may be connected to an EPC with a non-standalone gNB 1210A, via anXx interface between the PDCP 1206A and an NR RLC 1212A. The LTE eNB1201A may include protocol layers MAC 1202A, RLC 1203A and RLC 1204A,and PDCP 1205A and PDCP 1206A. An MCG bearer type may interface with thePDCP 1205A, and a split bearer type may interface with the PDCP 1206A.The gNB 1210A may include protocol layers NR MAC 1211A, NR RLC 1212A andNR RLC 1213A, and NR PDCP 1214A. An SCG bearer type may interface withthe NR PDCP 1214A.

A gNB 1201B may be an NG master base station, and an eLTE eNB 1210B maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The gNB1201B may be connected to an NGC with a non-standalone eLTE eNB 1210B,via an Xn interface between the NR PDCP 1206B and an RLC 1212B. The gNB1201B may include protocol layers NR MAC 1202B, NR RLC 1203B and NR RLC1204B, and NR PDCP 1205B and NR PDCP 1206B. An MCG bearer type mayinterface with the NR PDCP 1205B, and a split bearer type may interfacewith the NR PDCP 1206B. The eLTE eNB 1210B may include protocol layersMAC 1211B, RLC 1212B and RLC 1213B, and PDCP 1214B. An SCG bearer typemay interface with the PDCP 1214B.

An eLTE eNB 1201C may be an NG master base station, and a gNB 1210C maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The eLTE eNB1201C may be connected to an NGC with a non-standalone gNB 1210C, via anXn interface between the PDCP 1206C and an NR RLC 1212C. The eLTE eNB1201C may include protocol layers MAC 1202C, RLC 1203C and RLC 1204C,and PDCP 1205C and PDCP 1206C. An MCG bearer type may interface with thePDCP 1205C, and a split bearer type may interface with the PDCP 1206C.The gNB 1210C may include protocol layers NR MAC 1211C, NR RLC 1212C andNR RLC 1213C, and NR PDCP 1214C. An SCG bearer type may interface withthe NR PDCP 1214C.

In a 5G network, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. At least threealternatives may exist, for example, an MCG bearer, an SCG bearer, and asplit bearer, such as shown in FIG. 12A, FIG. 12B, and FIG. 12C. The NRRRC may be located in a master base station, and the SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may have at least one bearerconfigured to use radio resources provided by the secondary basestation. Tight interworking may or may not be configured or implemented.

The wireless device may be configured with two MAC entities: e.g., oneMAC entity for a master base station, and one MAC entity for a secondarybase station. In tight interworking, the configured set of serving cellsfor a wireless device may comprise of two subsets: e.g., the Master CellGroup (MCG) including the serving cells of the master base station, andthe Secondary Cell Group (SCG) including the serving cells of thesecondary base station.

At least one cell in a SCG may have a configured UL CC and one of them,for example, a PSCell (or the PCell of the SCG, which may also be calleda PCell), is configured with PUCCH resources. If the SCG is configured,there may be at least one SCG bearer or one split bearer. If one or moreof a physical layer problem or a random access problem is detected on aPSCell, if the maximum number of (NR) RLC retransmissions associatedwith the SCG has been reached, and/or if an access problem on a PSCellduring an SCG addition or during an SCG change is detected, then: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of the SCG may be stopped, a master basestation may be informed by the wireless device of a SCG failure type,and/or for a split bearer the DL data transfer over the master basestation may be maintained. The RLC AM bearer may be configured for thesplit bearer. Like the PCell, a PSCell may not be de-activated. A PSCellmay be changed with an SCG change, for example, with security key changeand a RACH procedure. A direct bearer type change, between a splitbearer and an SCG bearer, may not be supported. Simultaneousconfiguration of an SCG and a split bearer may not be supported.

A master base station and a secondary base station may interact. Themaster base station may maintain the RRM measurement configuration ofthe wireless device. The master base station may determine to ask asecondary base station to provide additional resources (e.g., servingcells) for a wireless device. This determination may be based on, forexample, received measurement reports, traffic conditions, and/or bearertypes. If a request from the master base station is received, asecondary base station may create a container that may result in theconfiguration of additional serving cells for the wireless device, orthe secondary base station may determine that it has no resourceavailable to do so. The master base station may provide at least part ofthe AS configuration and the wireless device capabilities to thesecondary base station, for example, for wireless device capabilitycoordination. The master base station and the secondary base station mayexchange information about a wireless device configuration such as byusing RRC containers (e.g., inter-node messages) carried in Xn or Xxmessages. The secondary base station may initiate a reconfiguration ofits existing serving cells (e.g., PUCCH towards the secondary basestation). The secondary base station may determine which cell is thePSCell within the SCG. The master base station may not change thecontent of the RRC configuration provided by the secondary base station.If an SCG is added and/or an SCG SCell is added, the master base stationmay provide the latest measurement results for the SCG cell(s). Eitheror both of a master base station and a secondary base station may knowthe SFN and subframe offset of each other by OAM, (e.g., for the purposeof DRX alignment and identification of a measurement gap). If a new SCGSCell is added, dedicated RRC signaling may be used for sending requiredsystem information of the cell, such as for CA, except, for example, forthe SFN acquired from an MIB of the PSCell of an SCG.

FIG. 13A and FIG. 13B show examples for gNB deployment. A core 1301 anda core 1310 may interface with other nodes via RAN-CN interfaces. In anon-centralized deployment example, the full protocol stack (e.g., NRRRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported at one node,such as a gNB 1302, a gNB 1303, and/or an eLTE eNB or LTE eNB 1304.These nodes (e.g., the gNB 1302, the gNB 1303, and the eLTE eNB or LTEeNB 1304) may interface with one of more of each other via a respectiveinter-BS interface. In a centralized deployment example, upper layers ofa gNB may be located in a Central Unit (CU) 1311, and lower layers ofthe gNB may be located in Distributed Units (DU) 1312, 1313, and 1314.The CU-DU interface (e.g., Fs interface) connecting CU 1311 and DUs1312, 1312, and 1314 may be ideal or non-ideal. The Fs-C may provide acontrol plane connection over the Fs interface, and the Fs-U may providea user plane connection over the Fs interface. In the centralizeddeployment, different functional split options between the CU 1311 andthe DUs 1312, 1313, and 1314 may be possible by locating differentprotocol layers (e.g., RAN functions) in the CU 1311 and in the DU 1312,1313, and 1314. The functional split may support flexibility to move theRAN functions between the CU 1311 and the DUs 1312, 1313, and 1314depending on service requirements and/or network environments. Thefunctional split option may change during operation (e.g., after the Fsinterface setup procedure), or the functional split option may changeonly in the Fs setup procedure (e.g., the functional split option may bestatic during operation after Fs setup procedure).

FIG. 14 shows examples for different functional split options of acentralized gNB deployment. Element numerals that are followed by “A” or“B” designations in FIG. 14 may represent the same elements in differenttraffic flows, for example, either receiving data (e.g., data 1402A) orsending data (e.g., 1402B). In the split option example 1, an NR RRC1401 may be in a CU, and an NR PDCP 1403, an NR RLC (e.g., comprising aHigh NR RLC 1404 and/or a Low NR RLC 1405), an NR MAC (e.g., comprisinga High NR MAC 1406 and/or a Low NR MAC 1407), an NR PHY (e.g.,comprising a High NR PHY 1408 and/or a LOW NR PHY 1409), and an RF 1410may be in a DU. In the split option example 2, the NR RRC 1401 and theNR PDCP 1403 may be in a CU, and the NR RLC, the NR MAC, the NR PHY, andthe RF 1410 may be in a DU. In the split option example 3, the NR RRC1401, the NR PDCP 1403, and a partial function of the NR RLC (e.g., theHigh NR RLC 1404) may be in a CU, and the other partial function of theNR RLC (e.g., the Low NR RLC 1405), the NR MAC, the NR PHY, and the RF1410 may be in a DU. In the split option example 4, the NR RRC 1401, theNR PDCP 1403, and the NR RLC may be in a CU, and the NR MAC, the NR PHY,and the RF 1410 may be in a DU. In the split option example 5, the NRRRC 1401, the NR PDCP 1403, the NR RLC, and a partial function of the NRMAC (e.g., the High NR MAC 1406) may be in a CU, and the other partialfunction of the NR MAC (e.g., the Low NR MAC 1407), the NR PHY, and theRF 1410 may be in a DU. In the split option example 6, the NR RRC 1401,the NR PDCP 1403, the NR RLC, and the NR MAC may be in CU, and the NRPHY and the RF 1410 may be in a DU. In the split option example 7, theNR RRC 1401, the NR PDCP 1403, the NR RLC, the NR MAC, and a partialfunction of the NR PHY (e.g., the High NR PHY 1408) may be in a CU, andthe other partial function of the NR PHY (e.g., the Low NR PHY 1409) andthe RF 1410 may be in a DU. In the split option example 8, the NR RRC1401, the NR PDCP 1403, the NR RLC, the NR MAC, and the NR PHY may be ina CU, and the RF 1410 may be in a DU.

The functional split may be configured per CU, per DU, per wirelessdevice, per bearer, per slice, and/or with other granularities. In a perCU split, a CU may have a fixed split, and DUs may be configured tomatch the split option of the CU. In a per DU split, each DU may beconfigured with a different split, and a CU may provide different splitoptions for different DUs. In a per wireless device split, a gNB (e.g.,a CU and a DU) may provide different split options for differentwireless devices. In a per bearer split, different split options may beutilized for different bearer types. In a per slice splice, differentsplit options may be applied for different slices.

A new radio access network (new RAN) may support different networkslices, which may allow differentiated treatment customized to supportdifferent service requirements with end to end scope. The new RAN mayprovide a differentiated handling of traffic for different networkslices that may be pre-configured, and the new RAN may allow a singleRAN node to support multiple slices. The new RAN may support selectionof a RAN part for a given network slice, for example, by one or moreslice ID(s) or NSSAI(s) provided by a wireless device or provided by anNGC (e.g., an NG CP). The slice ID(s) or NSSAI(s) may identify one ormore of pre-configured network slices in a PLMN. For an initial attach,a wireless device may provide a slice ID and/or an NSSAI, and a RAN node(e.g., a gNB) may use the slice ID or the NSSAI for routing an initialNAS signaling to an NGC control plane function (e.g., an NG CP). If awireless device does not provide any slice ID or NSSAI, a RAN node maysend a NAS signaling to a default NGC control plane function. Forsubsequent accesses, the wireless device may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. If the RAN resource isolation is implemented, shortageof shared resources in one slice does not cause a break in a servicelevel agreement for another slice.

The amount of data traffic carried over networks is expected to increasefor many years to come. The number of users and/or devices is increasingand each user/device accesses an increasing number and variety ofservices, for example, video delivery, large files, and images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum may be required for network operatorsto meet the increasing demand. Considering user expectations of highdata rates along with seamless mobility, it is beneficial that morespectrum be made available for deploying macro cells as well as smallcells for communication systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, if present, may be an effectivecomplement to licensed spectrum for network operators, for example, tohelp address the traffic explosion in some examples, such as hotspotareas. Licensed Assisted Access (LAA) offers an alternative foroperators to make use of unlicensed spectrum, for example, if managingone radio network, offering new possibilities for optimizing thenetwork's efficiency.

Listen-before-talk (clear channel assessment) may be implemented fortransmission in an LAA cell. In a listen-before-talk (LBT) procedure,equipment may apply a clear channel assessment (CCA) check before usingthe channel. For example, the CCA may utilize at least energy detectionto determine the presence or absence of other signals on a channel todetermine if a channel is occupied or clear, respectively. For example,European and Japanese regulations mandate the usage of LBT in theunlicensed bands. Apart from regulatory requirements, carrier sensingvia LBT may be one way for fair sharing of the unlicensed spectrum.

Discontinuous transmission on an unlicensed carrier with limited maximumtransmission duration may be enabled. Some of these functions may besupported by one or more signals to be transmitted from the beginning ofa discontinuous LAA downlink transmission. Channel reservation may beenabled by the transmission of signals, by an LAA node, after gainingchannel access, for example, via a successful LBT operation, so thatother nodes that receive the transmitted signal with energy above acertain threshold sense the channel to be occupied. Functions that mayneed to be supported by one or more signals for LAA operation withdiscontinuous downlink transmission may include one or more of thefollowing: detection of the LAA downlink transmission (including cellidentification) by wireless devices, time synchronization of wirelessdevices, and frequency synchronization of wireless devices.

DL LAA design may employ subframe boundary alignment according to LTE-Acarrier aggregation timing relationships across serving cells aggregatedby CA. This may not indicate that the eNB transmissions may start onlyat the subframe boundary. LAA may support transmitting PDSCH if not allOFDM symbols are available for transmission in a subframe according toLBT. Delivery of necessary control information for the PDSCH may also besupported.

LBT procedures may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum may require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, forexample, in Europe, specify an energy detection threshold such that if anode receives energy greater than this threshold, the node assumes thatthe channel is not free. Nodes may follow such regulatory requirements.A node may optionally use a lower threshold for energy detection thanthat specified by regulatory requirements. LAA may employ a mechanism toadaptively change the energy detection threshold, for example, LAA mayemploy a mechanism to adaptively change (e.g., lower or increase) theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. A Category4 LBT mechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. For some signals, insome implementation scenarios, in some situations, and/or in somefrequencies, no LBT procedure may performed by the transmitting entity.Category 2 (e.g., LBT without random back-off) may be implemented. Theduration of time that the channel is sensed to be idle before thetransmitting entity transmits may be deterministic. Category 3 (e.g.,LBT with random back-off with a contention window of fixed size) may beimplemented. The LBT procedure may have the following procedure as oneof its components. The transmitting entity may draw a random number Nwithin a contention window. The size of the contention window may bespecified by the minimum and maximum value of N. The size of thecontention window may be fixed. The random number N may be employed inthe LBT procedure to determine the duration of time that the channel issensed to be idle, for example, before the transmitting entity transmitson the channel. Category 4 (e.g., LBT with random back-off with acontention window of variable size) may be implemented. The transmittingentity may draw a random number N within a contention window. The sizeof contention window may be specified by the minimum and maximum valueof N. The transmitting entity may vary the size of the contention windowif drawing the random number N. The random number N may be used in theLBT procedure to determine the duration of time that the channel issensed to be idle, for example, before the transmitting entity transmitson the channel.

LAA may employ uplink LBT at the wireless device. The UL LBT scheme maybe different from the DL LBT scheme, for example, by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

LAA may use uplink LBT at the wireless device. The UL LBT scheme may bedifferent from the DL LBT scheme, for example, by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

A DL transmission burst may be a continuous transmission from a DLtransmitting node, for example, with no transmission immediately beforeor after from the same node on the same CC. An UL transmission burstfrom a wireless device perspective may be a continuous transmission froma wireless device, for example, with no transmission immediately beforeor after from the same wireless device on the same CC. A UL transmissionburst may be defined from a wireless device perspective or from a basestation perspective. If a base station is operating DL and UL LAA overthe same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. An instant in time may be part of a DLtransmission burst or part of an UL transmission burst.

A wireless device may use at least one wireless device (e.g., UE)procedure for receiving control information described herein for a MCGand a SCG (e.g., if the wireless device is configured with an SCG). Theterms ‘secondary cell,’ ‘secondary cells,’ ‘serving cell,’ ‘servingcells’ may refer to secondary cell, secondary cells, serving cell,and/or serving cells belonging to the MCG, respectively, for example, ifthe at least one procedure is used for MCG. The terms ‘secondary cell,’‘secondary cells,’ ‘serving cell,’ ‘serving cells’ may refer tosecondary cell, secondary cells (which may or may not include a PSCell),serving cell, and/or serving cells belonging to the SCG, respectively,for example, if the at least one procedure is used for SCG. The term‘primary cell’ associated with the SCG may refer to the PSCell of theSCG.

A wireless device that is configured for operation in bandwidth parts(BWPs) of a cell may be configured, by one or more higher layers for thecell, with a set of one or more BWPs (e.g., which may be up to four BWPsor any other number of BWPs). The set of one or more BWPs may comprise aset of one or more DL BWPs for receptions by the wireless device (DL BWPset) in a DL bandwidth by at least one parameter DL-BWP for the cell andmay comprise a set of one or more UL BWPs (e.g., which may be up to fourBWPs or any other number of BWPs) for transmissions by the wirelessdevice (UL BWP set) in an UL bandwidth by at least one parameter UL-BWPfor the cell.

An initial active DL BWP may be defined by at least one of a locationand number of contiguous PRBs, a subcarrier spacing, and/or a cyclicprefix, for the control resource set for Type0-PDCCH common searchspace. For operation on the primary cell, a wireless device may beprovided, by one or more higher layer parameters, with an initial ULBWP. The initial UL BWP may be for a random access procedure. Thewireless device may be configured with an initial BWP for a randomaccess procedure on a supplementary (or secondary) uplink carrier on theprimary cell, for example, if the wireless device is configured with thesupplementary (or secondary) uplink carrier.

For unpaired spectrum operation, a wireless device may expect that acenter frequency for a DL BWP may be the same as a center frequency fora UL BWP. For example, for a DL BWP or a UL BWP in a set of one or moreDL BWPs or one or more UL BWPs, respectively, the wireless device may beconfigured, for a cell, with one or more parameters indicating at leastone of the following: a subcarrier spacing (e.g., provided by a higherlayer parameter DL-BWP-mu or UL-BWP-mu); a cyclic prefix (e.g., providedby a higher layer parameter DL-BWP-CP or UL-BWP-CP); a number ofcontiguous PRBs (e.g., provided by a higher layer parameter DL-BWP-BWand/or UL-BWP-BW); an index in the set of one or more DL BWPs and/or oneor more UL BWPs (e.g., provided by respective higher layer parametersDL-BWP-index and UL-BWP-index for a paired spectrum operation) or a linkbetween a DL BWP and an UL BWP from the set of configured DL BWPs and ULBWPs (e.g., provided by higher layer parameter BWP-pair-index for anunpaired spectrum operation); a DCI (e.g., DCI 1_0 and/or DCI 1_1)detection to a PDSCH reception timing by higher layer parameterDL-data-time-domain, a PDSCH reception to a HARQ-ACK transmission timingvalue by higher layer parameter DL-data-DL-acknowledgement, a DCI (e.g.,DCI 0_0 and/or DCI 0_1) detection to a PUSCH transmission timing valueby higher layer parameter UL-data-time-domain; and/or an offset of thefirst PRB of the DL bandwidth or the UL bandwidth, respectively,relative to the first PRB of a bandwidth by higher layer parameterDL-BWP-loc or UL-BWP-loc. For the downlink of the primary cell, thefirst PRB of the bandwidth may be the first RPB of the SS/PBCH blockused by the wireless device for an initial cell selection. For theuplink of the primary cell for a paired spectrum operation, the firstPRB of the bandwidth may be the first PRB of the UL bandwidth indicatedby SystemInformationBlockType1. For the uplink of the primary cell forunpaired, the first PRB of the bandwidth may be the first PRB of theSS/PBCH block used by the wireless device for an initial cell selection.For a secondary cell or carrier, the first PRB of the DL bandwidth (orof the UL bandwidth) may be indicated to the wireless device by thehigher layer configuration for the secondary cell or carrier.

For a DL BWP in a set of one or more DL BWPs on the primary cell, awireless device may be configured with one or more control resource setsfor at least one type of common search space and for at least onewireless-device-specific search space (e.g., a UE-specific searchspace). For example, the wireless device may not be configured without acommon search space on the PCell, or on the PSCell, in the active DLBWP. For a UL BWP in a set of one or more UL BWPs, the wireless devicemay be configured with one or more resource sets for one or more PUCCHtransmissions.

A wireless device may receive a PDCCH and/or PDSCH in a DL BWP based ona configured subcarrier spacing and CP length for the DL BWP. Thewireless device may transmit a PUCCH and/or PUSCH in a UL BWP based on aconfigured subcarrier spacing and CP length for the UL BWP.

If a DCI (e.g., DCI format 1_1) comprises a BWP indicator field, the BWPindicator field value may indicate an active DL BWP, from the configuredDL BWP set, for one or more DL receptions. If a DCI (e.g., DCI format0_1) comprises a BWP indicator field, the BWP indicator field value mayindicate an active UL BWP, from the configured UL BWP set, for one ormore UL transmissions.

For the primary cell, a wireless device may be provided, by a higherlayer parameter, with Default-DL-BWP that may indicate a default DL BWPamong the configured DL BWPs. If a wireless device is not provided witha default DL BWP (e.g., the Default-DL-BWP), the default DL BWP may bethe initial active DL BWP.

A wireless device may be provided, by a higher layer parameter, withBWP-InactivityTimer that may indicate a timer value for the primarycell. The wireless device may start the timer, for example, if thewireless device detects a DCI (e.g., DCI format 1_1) indicating anactive DL BWP, other than the default DL BWP, for a paired spectrumoperation or if the wireless device detects a DCI (e.g., DCI format 1_1or DCI format 0_1) indicating an active DL BWP or UL BWP, other than thedefault DL BWP or UL BWP, for an unpaired spectrum operation. Thewireless device may increment the timer value in increments of a firstvalue (e.g., the first value may be 1 millisecond) for carrierfrequencies smaller than or equal to 6 GHz or in increments of a secondvalue (e.g., the second value may be 0.5 milliseconds) for carrierfrequencies larger than 6 GHz, for example, if the wireless device doesnot detect a DCI (e.g., DCI format 1_1) for a paired spectrum operationor if the wireless device does not detect a DCI (e.g., DCI format 1_1 orDCI format 0_1) for an unpaired spectrum operation during the intervalof each increment. The timer may expire, for example, if the timer valueis equal to the BWP-InactivityTimer value. The wireless device mayswitch to the default DL BWP from an active DL BWP, for example, if thetimer expires.

One or more procedures of a wireless device on a secondary cell (e.g.,one or more wireless device procedures on a secondary cell) may be thesame or similar to one or more procedures on a primary cell, forexample, if the wireless device is configured for the secondary cellwith a higher layer parameter (e.g., Default-DL-BWP) indicating adefault DL BWP among the configured DL BWPs and/or the wireless deviceis configured with a higher layer parameter (e.g., BWP-InactivityTimer)indicating a timer value. The one or more procedures of the wirelessdevice on the secondary cell may be similar to one or more procedures onthe primary cell, but the one or more procedures of the wireless deviceon the secondary cell may use the timer value for the secondary cell andthe default DL BWP for the secondary cell.

If a wireless device is configured by a higher layer parameter (e.g.,Active-BWP-DL-SCell) that may indicate a first active DL BWP and/or by ahigher layer parameter (e.g., Active-BWP-UL-SCell) that may indicate afirst active UL BWP on a secondary cell or carrier, the wireless devicemay use the indicated DL BWP and the indicated UL BWP on the secondarycell as the respective first active DL BWP and first active UL BWP onthe secondary cell or carrier.

For a paired spectrum operation, a wireless device may not transmit anHARQ-ACK, for example, if the wireless device changes its active UL BWPbetween a time of a detection of a DCI (e.g., DCI format 1_1) and a timeof a corresponding HARQ-ACK transmission. A wireless device may monitora PDCCH, for example, while the wireless device performs measurementsover a bandwidth that may not be within the DL BWP for the wirelessdevice.

A base station may transmit a DCI to a wireless device to provide thewireless device with DL and/or UL transmission information. The DLand/or UL transmission information may indicate at least one of thefollowing: scheduling of a PUSCH, scheduling of a PDSCH, a slot(mini-slot, and/or subframe) format, TPC commands for a PUSCH, PUCCH,and/or SRS transmission. The DCI may comprise at least one of: a carrierindicator, an identifier for DCI formats, one or more downlinkscheduling assignments, one or more uplink scheduling grants, one ormore power-control commands (TPCs), one or more slot format indicators,and/or one or more pre-emption indications.

The DL and/or UL transmission information may comprise one or moreparameters (or fields) indicating at least one of the following:frequency domain and/or time domain resource assignment(s), frequencyhopping flag, modulation and coding scheme (MCS), new data indicator(NDI), redundancy version (RV), HARQ process number, TPC command for aPUSCH and/or PUCCH, UL/SUL indicator, bandwidth part (BWP) indicator,VRB-to-PRB mapping, a downlink assignment index, n-th downlinkassignment index (where n>0), SRS resource indicator, precodinginformation and number of layers, antenna ports, CSI request, CBGtransmission information, PTRS-DMRS association, beta-offset indicator,DMRS sequence initialization, PUCCH resource indicator, PDSCH-to-HARQfeedback timing indicator, PRB bundling size indicator, a rate matchingindicator, ZP CSI-RS trigger, a transmission configuration indication,an SRS request, CBG flushing out information, one or more Identifiersfor DCI formats, one or more slot format indicators, one or morepre-emption indications, one or more TPC command numbers, one or moreblock numbers, one or more identifiers for DCI formats, PDSCH resourceindication, a transport format, HARQ information, control informationrelated to multiple antenna schemes, a command for power control of thePUCCH (e.g., used for transmission of ACK/NACK in response to downlinkscheduling assignments), HARQ related information, a power controlcommand of the PUSCH, and/or any combination thereof.

The DCI may have one or more formats or types. Message sizes of the oneor more formats may be the same. Message sizes of the one or moreformats may be different. A plurality of DCIs having the same messageformat (and/or size) may comprise the same control information. Aplurality of DCIs having the same message format (and/or size) maycomprise the different control information. A plurality of DCIs havingdifferent message formats (and/or sizes) may comprise the same controlinformation. A plurality of DCIs having different message formats(and/or sizes) may comprise the different control information. Forexample, supporting spatial multiplexing with noncontiguous allocationof RBs in the frequency domain may require a larger size of schedulingmessage in comparison with an uplink grant for frequency-contiguousallocation. The DCI may be categorized into different DCI formats. EachDCI format may correspond to a certain message size and/or usage.

FIG. 15 shows an example of one or more DCI formats. Any other DCIformat for any other use, or combinations of uses, may be implemented.

FIG. 16 shows an example of one or more DCI formats. DCI format 0_0 maybe used for scheduling of a PUSCH in one cell. For example, the DCIformat 0_0 may comprise one or more fields indicating at least one ofthe following: identifier for DCI formats (e.g., 1 bit); frequencydomain resource assignment (e.g., N bits—variable with UL BWP N_RB);time domain resource assignment (e.g., X bits—the bitwidth may beassociated with the row indexes in pusch_allocationList in RRC);frequency hopping flag (e.g., 1 bit); modulation and coding scheme(e.g., 5 bits); new data indicator (e.g., 1 bit); redundancy version(e.g., 2 bits); HARQ process number (e.g., 4 bits); TPC command forscheduled PUSCH (e.g., 2 bits); and/or UL/SUL indicator (e.g., 0 bit forwireless devices not configured with SUL in the cell, and 1 bit forwireless devices configured with SUL in the cell); zeros may be appendedto format 0_0 until the payload size equals that of format 1_0, forexample, if the number of information bits in format 0_0 is less thanthe payload size of format 1_0 for scheduling the same serving cell.

DCI format 0_1 may be used for the scheduling of a PUSCH in one cell.The DCI format 0_1 may comprise one or more fields indicating at leastone of the following: carrier indicator (e.g., 0 or 3 bits); identifierfor DCI formats (e.g., 1 bit); bandwidth part indicator (e.g., 0, 1 or 2bits—the bitwidth for this field may be determined based on the higherlayer parameter BandwidthPart-Config for the PUSCH); frequency domainresource assignment (e.g., the bitwidth may be variable with a resourceallocation type; time domain resource assignment (e.g., X—bits thebitwidth may be associated with the row indexes in pusch_allocationListin RRC); VRB-to-PRB mapping (e.g., 0 or 1 bit; for example, applicableto resource allocation type 1 (e.g., 0 bit) if only resource allocationtype 0 is configured and 1 bit otherwise); frequency hopping flag (e.g.,0 or 1 bit; for example, applicable to resource allocation type 1 (e.g.,0 bit) if only resource allocation type 0 is configured and 1 bitotherwise); modulation and coding scheme (e.g., 5 bits); new dataindicator (e.g., 1 bit); redundancy version (e.g., 2 bits); HARQ processnumber (e.g., 4 bits); 1st downlink assignment index (e.g., 1 bit forsemi-static HARQ-ACK codebook, and 2 bits for dynamic HARQ-ACK codebookwith single HARQ-ACK codebook); 2nd downlink assignment index (e.g., 2bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks, and0 bit otherwise); TPC command for a scheduled PUSCH (e.g., 2 bits); SRSresource indicator (e.g., variable bits that may be determined byRRC_Parameter_SRS-SetUse); precoding information and number of layers(e.g., 0, 2, 3, 4, 5, or 6 bits); antenna ports (e.g., 2, 3, 4, or 5bits); SRS request (e.g., 2 bits); CSI request (e.g., 0, 1, 2, 3, 4, 5,or 6 bits determined by higher layer parameter ReportTriggerSize); CBGtransmission information (e.g., 0, 2, 4, 6, or 8 bits determined byhigher layer parameter maxCodeBlockGroupsPerTransportBlock for PUSCH);PTRS-DMRS association (e.g., 0 or 2 bits); beta_offset indicator (e.g.,0 bit if the higher layer parameter dynamic in uci-on-PUSCH is notconfigured; otherwise 2 bits); DMRS sequence initialization (e.g., 0 or1 bit); and/or UL/SUL indicator (e.g., 0 bit for wireless devices notconfigured with SUL in the cell, and 1 bit for wireless devicesconfigured with SUL in the cell).

DCI format 1_0 may be used for the scheduling of a PDSCH in one DL cell.The DCI format 1_0 may comprise one or more fields indicating at leastone of the following: an identifier for DCI formats (e.g., 1 bit);frequency domain resource assignment (e.g., variable with DL BWP N_RB);time domain resource assignment (e.g., X bits—The bitwidth may beassociated with the row indexes in pusch_allocationList in RRC);VRB-to-PRB mapping (e.g., 1 bit); modulation and coding scheme (e.g., 5bits); new data indicator (e.g., 1 bit); redundancy version (e.g., 2bits); HARQ process number (e.g., 4 bits); downlink assignment index(e.g., 2 bits); TPC command for a scheduled PUCCH (e.g., 2 bits); PUCCHresource indicator (e.g., 2 or 3 bits); or PDSCH-to-HARQ_feedback timingindicator (e.g., 3 bits). The DCI format 1_0 may comprise one or moredifferent fields, one or more different bitwidths, and/or one or moredifferent values for one or more fields, for example, if the DCI format1_0 is with CRC scrambled by different types of RNTI.

DCI format 1_1 may be used for the scheduling of a PDSCH in one cell.The DCI format 1_1 may comprise one or more fields indicating at leastone of the following: carrier indicator (e.g., 0 or 3 bits); identifierfor DCI formats (e.g., 1 bit); bandwidth part indicator (e.g., 0, 1 or 2bits; the bitwidth for this field may be determined according to thehigher layer parameter BandwidthPart-Config for the PDSCH); frequencydomain resource assignment (e.g., variable bits with a resourceallocation type); time domain resource assignment (e.g., 1, 2, 3, or 4bits—the bitwidth may be associated with the row indexes inpusch_allocationList in RRC); VRB-to-PRB mapping (e.g., applicable toresource allocation type 1 (e.g., 0 bit) if only resource allocationtype 0 is configured, and 1 bit otherwise); PRB bundling size indicator(e.g., 0 bit if the higher layer parameter PRB_bundling=OFF or 1 bit ifthe higher layer parameter PRB_bundling=ON); rate matching indicator (0,1, or 2 bits); and/or ZP CSI-RS trigger (0, 1, or 2 bits). The DCIformat 1_1 may comprise one or more other fields (e.g., one or moreadditional fields). For example, for transport block 1, the DCI format1_1 may comprise modulation and coding scheme (e.g., 5 bits), new dataindicator (e.g., 1 bit), redundancy version (e.g., 2 bits). Fortransport block 2, the DCI format 1_1 may comprise modulation and codingscheme (e.g., 5 bits), new data indicator (e.g., 1 bit), redundancyversion (e.g., 2 bits). The DCI format 1_1 may comprise HARQ processnumber (e.g., 4 bits); downlink assignment index (e.g., 0, 2, or 4bits); TPC command for scheduled PUCCH (e.g., 2 bits); PUCCH resourceindicator (e.g., 2 or 3 bits); PDSCH-to-HARQ_feedback timing indicator(e.g., 0, 1, 2, or 3 bits); antenna port(s) (e.g., 1, 2, 3, 4, 5, or 6bits—the number of CDM groups without data of values 1, 2, and 3 mayrefer to CDM groups {0}, {0, 1}, and {0, 1, 2} respectively);transmission configuration indication (e.g., 0 or 3 bits); SRS request(e.g., 2 or 3 bits); CBG transmission information (e.g., 0, 2, 4, 6, or8 bits); CBG flushing out information (e.g., 0 or 1 bit); and/or DMRSsequence initialization (e.g., 1 bit).

DCI format 2_0 may be used for notifying the slot format. The DCI format2_0 may comprise one or more fields indicating at least one of thefollowing: an identifier for DCI formats (e.g., 1 bit); and/or one ormore slot format indicator (e.g., slot format indicator 1, slot formatindicator 2, . . . , slot format indicator N). The size of DCI format2_0 may be configurable by higher layers. For example, the bit size ofthe slot format indicator field may be determined by an RRC message.

DCI format 2_1 may be used for notifying the PRB(s) and OFDM symbol(s)where a wireless device may assume no transmission is intended for thewireless device. The DCI format 2_1 may comprise one or more fieldsindicating at least one of the following: an identifier for DCI formats(e.g., 1 bit); and/or one or more pre-emption indication (e.g.,pre-emption indication 1, pre-emption indication 2, . . . , pre-emptionindication N). The size of DCI format 2_1 may be configurable by higherlayers, and a pre-emption indication may be 14 bits.

DCI format 2_2 may be used for the transmission of TPC commands forPUCCH and PUSCH. The DCI format 2_2 may comprise one or more fieldsindicating at least one of the following: an identifier for DCI formats(e.g., 1 bit); and/or one or more TPC command numbers (e.g., TPC commandnumber 1, TPC command number 2, . . . , TPC command number N) The indexto the TPC command number for a cell may be determined by one or moreparameters provided by higher layers, and a TPC command number may be 2bits.

DCI format 2_3 may be used for the transmission of a group of TPCcommands for SRS transmissions by one or more wireless devices. Alongwith a TPC command, an SRS request may also be transmitted. The DCIformat 2_3 may comprise one or more fields indicating at least one ofthe following: an identifier for DCI formats (e.g., 1 bit); and/or oneor more block numbers (e.g., block number 1, block number 2, . . . ,block number B) The starting position of a block may be determined bythe parameter startingBitOfFormat2_3 provided by higher layers for thewireless device configured with the block. For a UL without PUCCH andPUSCH or a UL on which the SRS power control is not tied with PUSCHpower control, one block may be configured for the wireless device byhigher layers, with the following fields defined for the block: an SRSrequest (e.g., 0 or 2 bits), and/or TPC command number (e.g., 2 bits).

One or more DCI formats for downlink scheduling may be organized intodifferent groups based on the presence or absence of one or more fields.The one or more fields may vary between DCI formats. For example, theone or more fields may indicate at least one of: resource information(e.g., carrier indicator, RB allocation, etc.); HARQ process number;MCS, NDI, and a first RV (e.g., RV for the first TB); MCS, NDI, and asecond RV (e.g., RV for the second TB); MIMO related information (e.g.,at least one of: PMI, precoding information, transport block swap flag,power offset between PDSCH and reference signal, reference-signalscrambling sequence, number of layers, and/or antenna ports for thetransmission); PDSCH resource-element mapping and QCI; downlinkassignment index (DAI); TPC for PUCCH; SRS request for triggering SRStransmission; ACK/NACK offset; DCI format indication used to distinguishone or more DCI formats from each other (e.g., between DCI 0 and DCI1A); any combination thereof; and/or padding.

One or more DCI formats for uplink scheduling may be organized intodifferent groups with the presence or absence of one or more fields. Theone or more fields may vary between DCI formats. For example, the one ormore fields may indicate at least one of: resource information (e.g.,carrier indicator, resource allocation type, RB allocation, etc.); MCSand a first NDI (e.g., NDI for the first TB); MCS and a second NDI(e.g., NDI for the second TB); Phase rotation of the uplink DM-RS;precoding information; CSI request for requesting an aperiodic CSIreport; SRS request used to trigger aperiodic SRS transmission based onone or more settings semi-statically configured, predefined, and/orpreconfigured; uplink index/DAI; TPC for PUSCH; DCI format indicationused to distinguish one or more DCI formats from each other (e.g.,between DCI 0 and DCI 1A); any combination thereof; and/or padding.

A wireless device may monitor for one or more PDCCHs to detect one ormore DCIs. The one or more PDCCHs may be associated with a common searchspace (CSS) and/or a device-specific search space (e.g., UE-specificsearch space (USS)). A wireless device may monitor for one or morePDCCHs comprising one or more DCI formats. A power consumption at awireless device may increase as the number of DCI formats used for PDCCHmonitoring increases. Monitoring for a PDCCH associated with a limitednumber of DCI formats may save power consumption. For example, a firstDCI format may be used for an eMTC wireless device. If a type of awireless device is not eMTC, the wireless device may not monitor for aPDCCH at least with the first DCI, for example, to save powerconsumption.

A base station may transmit one or more PDCCHs in different controlresource sets, for example, to support wide bandwidth operation (e.g.,in an NR system). A base station may transmit one or more RRC messagescomprising configuration parameters of one or more control resourcesets. The one or more control resource sets may comprise at least oneof: a first OFDM symbol (e.g., CORESET_StartSymbol); a number ofconsecutive OFDM symbols (e.g., CORESET_NumSymbol); a set of resourceblocks (e.g., CORESET_RBSet); a CCE-to-REG mapping (e.g.,CORESET_mapping); and/or a REG bundle size for interleaved CCE-to-REGmapping (e.g., CORESET_REG_bundle). A wireless device may monitor for aPDCCH to detect at least one DCI, for example, based on configuredcontrol resource sets.

A wireless device may monitor for at least one set of one or more PDCCHcandidates, in one or more control resource sets, on at least one activeDL BWP on one or more activated serving cells according to correspondingsearch spaces. The monitoring may imply and/or comprise decoding of atleast one of the one or more PDCCH candidates according to the monitoredDCI formats.

A wireless device may be configured by higher layer parameterSSB-periodicity-serving-cell a periodicity of half frames fortransmission of SS/PBCH blocks in a serving cell. A wireless device mayreceive a PDCCH by excluding REs corresponding to SS/PBCH block indexesindicated by SSB-transmitted-SIB1, for example, if the wireless devicehas received SSB-transmitted-SIB1 and has not received SSB-transmittedand if REs for the PDCCH reception overlap with REs corresponding toSS/PBCH block indexes indicated by SSB-transmitted-SIB1. A wirelessdevice may receive a PDCCH by excluding REs corresponding to SS/PBCHblock indexes indicated by SSB-transmitted, for example, if the wirelessdevice has received SSB-transmitted and if REs for the PDCCH receptionoverlap with REs corresponding to SS/PBCH block indexes indicated bySSB-transmitted.

A wireless device may transmit, in a device capability parameter (e.g.,UE-NR-Capability), an indication for a number of PDCCH candidates thatthe wireless device may monitor per slot (mini-slot, and/or subframe),for example, if the wireless device is configured for carrieraggregation operation over more than one or more cells. The wirelessdevice may transmit the indication, for example, based on a carrieraggregation capability for a wireless device being larger than athreshold. The device capability parameter may comprise one or moreparameters indicating the carrier aggregation capability. A wirelessdevice may not be configured with a number of PDCCH candidates tomonitor per slot (mini-slot, and/or subframe) that is larger than asecond threshold (e.g., the second threshold may indicate a maximumnumber), for example, if the wireless device is configured for carrieraggregation operation over more than one cell.

A base station may configure a wireless device with one or more time andfrequency resources that may be used to report a channel stateinformation (CSI). The CSI may comprise at least one of Channel QualityIndicator (CQI), preceding matrix indicator (PMI), CSI-RS resourceindicator (CRI), strongest layer indication (SLI), rank indication (RI)and/or L1-RSRP.

For CQI, PMI, CRI, SLI, RI, and/or L1-RSRP, a wireless device may beconfigured by higher layers with at least one of N≥1 ReportConfigReporting Settings, M≥1 ResourceConfig Resource Settings, and/or atleast one MeasConfig measurement setting containing L≥1 Links. The atleast one MeasConfig may comprise at least one of: a list of one or morereporting configurations (ReportConfigList), a list of one or moreresource configurations (ResourceConfigList), a list of one or more linkconfigurations (MeasLinkConfigList) and/or a list of one or more triggerstates (ReportTrigger).

A reporting setting (e.g., ReportConfig) may be associated with at leastone DL BWP (e.g., the at least one DL BWP may be indicated by a higherlayer parameter, for example, bandwidthPartId). The reporting settingmay comprise one or more reported parameter(s) for at least one CSIreporting band: CSI Type (I or II) if reported, at least one codebookconfiguration comprising codebook subset restriction, time-domainbehavior, frequency granularity for CQI and PMI, measurement restrictionconfigurations, the strongest layer indicator (SLI), the reportedL1-RSRP parameter(s), CRI, and/or SSB Resource Indicator (SSBRI). TheReportConfig may comprise a ReportConfigID to identify the ReportConfig,a ReportConfigType to indicate the time domain behavior of the report(either aperiodic, semi-persistent, or periodic), a ReportQuantity toindicate the CSI-related or L1-RSRP-related quantities to report, and/ora ReportFreqConfiguration to indicate the reporting granularity in thefrequency domain. For periodic/semi-persistent reporting, a ReportConfigmay comprise a ReportSlotConfig to indicate at least the periodicity anda slot offset. For aperiodic reporting, a ReportConfig may comprise anAperiodicReportSlotOffset to indicate at least a set of allowed valuesof the timing offset for aperiodic reporting (e.g., a particular valuemay be indicated in DCI). The ReportFreqConfiguration may comprise oneor more parameters to enable at least one configuration of at leastsubband or wideband PMI and CQI reporting. The ReportConfig may compriseMeasRestrictionConfig-time-channel to indicate at least parameters toenable at least one configuration of time domain measurement restrictionfor a channel. The ReportConfig may compriseMeasRestrictionConfig-time-interference to indicate one or moreparameters to enable separate configuration of time domain measurementrestriction for interference. The ReportConfig may compriseCodebookConfig, which may comprise one or more configuration parametersfor Type-I or Type II CSI comprising codebook subset restriction.

A Resource Setting (e.g., ResourceConfig) may comprise at least oneconfiguration of S≥1 CSI-RS Resource Sets (e.g., a higher layerparameter ResourceSetConfig), with Resource Set comprising one or moreCSI-RS resources (e.g., higher layer parametersNZP-CSI-RS-ResourceConfigList and CSI-IM-ResourceConfigList) and one ormore SS/PBCH Block resources for L1-RSRP computation (e.g., higher layerparameter resource-config-SS-list). The Resource setting may be locatedin the BWP identified by the higher layer parameter (e.g., BWP-info),and one or more linked Resource Settings of a CSI Report Setting mayhave the same BWP. For periodic and semi-persistent CSI ResourceSettings, S may be 1. At least one of S≥1 CSI-RS Resource Sets maycomprise one or more CSI-RS resources (Ks≥1, e.g., higher layerparameter CSI-RS-ResourceConfig), each of which may comprise one or moreparameters indicating at least mapping to REs and number of ports andtime-domain behavior. The time domain behavior of the one or more CSI-RSresources, which may be part of one or more sets within a CSI-RSresource setting, may be indicated by the higher layer parameterResourceConfigType and may be aperiodic, periodic, or semi-persistent.At least one of the following may be configured via higher layersignaling for one or more CSI resource settings for channel andinterference measurement: one or more CSI-IM resources for interferencemeasurement, one or more non-zero power CSI-RS resources forinterference measurement, and/or one or more non-zero power CSI-RSresources for channel measurement.

A Link MeasLinkConfig in the higher layer-configured CSI measurementsetting may comprise the CSI reporting setting indication, CSI resourcesetting indication, and/or a measurement quantity (e.g., MeasQuantity)that may be an indication of the quantity to be measured, which may beeither channel measurement or interference measurement. ReportConfigMaxmay indicate the maximum number of report configurations.ResourceConfigMax may indicate the maximum number of resourceconfigurations. MeasLinkConfigMax may indicate the maximum number oflink configurations. ResourceSetMax may indicate the maximum number ofresources sets per resource configuration. CSI-RS-ResourcePerSetMax mayindicate the maximum number of NZP-CS I-RS resources per NZP-CSI-RSresource set. NZP-CSI-RS-ResourceMax may indicate the maximum number ofNZP-CSI-RS resources. CSI-IM-ResourcePerSetMax may indicate the maximumnumber of CSI-IM resources per CSI-IM resource set. CSI-IM-ResourceMaxmay indicate the maximum number of CSI-IM resources.AperiodicReportTrigger may comprise one or more trigger states fordynamically selecting one or more aperiodic reporting configurations.

A reporting configuration for CSI may be aperiodic (e.g., using PUSCH),periodic (e.g., using PUCCH) or semi-persistent (e.g., using PUCCHand/or DCI activated PUSCH). The CSI-RS Resources may be periodic,semi-persistent, or aperiodic.

FIG. 17 shows an example of CSI-RS configurations (e.g., a table fortriggering/activation of CSI Reporting for possible CSI-RSConfigurations). FIG. 17 shows examples of the supported combinations ofCSI Reporting configurations and CSI Resource configurations and how theCSI Reporting may be triggered for each CSI-RS configuration. Forexample, the periodic CSI-RS may configured by higher layers (e.g.,RRC). The semi-persistent CSI-RS may be activated and deactivated. Theaperiodic CSI-RS may be configured and selected.

A single CQI may be reported for one codeword per CSI report, forexample, if a wireless device is configured with the higher layerconfigured parameter Number-CQI set to ‘1’. One CQI for each codewordmay be reported per CSI report, for example, if a wireless device isconfigured with the higher layer configured parameter Number-CQI set to‘2’. The ReportConfig may comprise the Number-CQI.

A wireless device may determine a CRI from the supported set of CRIvalues and may report the number in each CRI report, for example, if thewireless device is configured with a CSI-RS resource set and the higherlayer parameter CSI-RS-ResourceRep is set to ‘OFF’. CRI may not bereported, for example, if the higher layer parameter CSI-RS-ResourceRepis set to ‘ON’.

For periodic and/or semi-persistent CSI reporting, the followingperiodicities (measured in slots) may be configured by the higher layerparameter ReportPeriodicity. For example, ReportPeriodicity may indicateone of values from the set {5, 10, 20, 40, 80, 160, 320}.

A wireless device may not be required to update measurements for morethan 64 CSI-RS and/or SSB resources, for example, if the wireless deviceis configured with the higher layer parameter ReportQuantity set to‘CRI/RSRP’ and the wireless device is configured with the higher layerparameter group-based-beam-reporting set to ‘OFF’. For example, thewireless device may report in a single report nrofReportedRS (higherlayer configured) different CRI and/or SSBRI (SSB Resource Indicator)for each report setting. The reported L1-RSRP value may be defined by a7-bit value in the range [−140, −44] dBm with 1 dB step size, forexample, if the higher layer parameter nrofReportedRS is configured tobe one. The wireless device may use largest L1-RSRP and differentialL1-RSRP based reporting, for example, if the higher layer parameternrofReportedRS is configured to be larger than one. The largest value ofL1-RSRP may use, for example, a 7-bit value and the differential L1-RSRPmay use, for example, a 4-bit value. The differential L1-RSRP values maybe computed with 2 dB step size with a reference to the largest L1-RSRPvalue, which may be part of the same L1-RSRP reporting instance.

A wireless device may report in a single reporting instance up tonumber-of-beams-reporting L1-RSRP and CSI reports, for example, if thewireless device is configured with the higher layer parameterReportQuantity set to ‘CRI/RSRP’ and the wireless device is configuredwith the higher layer parameter group-based-beam-reporting set to ‘ON.’Up to number-of-beams-reporting, CSI-RS and/or SSB resources may bereceived simultaneously by the wireless device either with a singlespatial domain receive filter or with multiple simultaneous spatialdomain receive filters.

For L1-RSRP computation, the wireless device may be configured withCSI-RS resources, SS/PBCH Block resources, or both CSI-RS and SS/PBCHBlock resources. For L1-RSRP computation, the wireless device may beconfigured with CSI-RS resource setting up to 16 CSI-RS resource setshaving up to 64 resources within each set. The total number of differentCSI-RS resources over all resource sets may be, for example, no morethan 128 (or up to any other number).

A wireless device may not report information (e.g., a quantity for theReportConfig associated with a higher layer parameter ReportQuantity),for example, if the wireless device is configured with a CSI-RS resourceand configured with the higher layer parameter ReportQuantity set to ‘NoReport.’ Otherwise, the wireless device may report the information asconfigured by the ReportQuantity.

The ReportFreqConfiguration in a ReportConfig may indicate the frequencygranularity of the CSI Report. For CSI reporting, a wireless device maybe configured via higher layer signaling with one out of two possiblesubband sizes. A subband may be defined as N_(PRB) ^(SB) contiguous PRBsand may depend on the total number of PRBs in the carrier bandwidth partbased on one or more configurable subband sizes.

FIG. 18 is an example of configurable subband sizes. A CSI reportingsetting configuration may define a CSI reporting band as a subset of oneor more subbands of the bandwidth part. The ReportFreqConfiguration mayindicate one or more of: the CSI-ReportingBand as a contiguous ornon-contiguous subset of subbands in the bandwidth part for which CSImay be reported (e.g., the wireless device may not be configured with aCSI reporting band which may comprise one or more subbands wherereference signals for channel and interference may not be present.);single CQI or multiple CQI reporting, as configured by the higher layerparameter CQI-FormatIndicator (e.g., if single CQI reporting isconfigured, a single CQI may be reported for each codeword for theentire CSI reporting band. If multiple CQI reporting is configured, oneCQI for each codeword may be reported for each subband in the CSIreporting band.); and/or single PMI or multiple PMI reporting asconfigured by the higher layer parameter PMI-FormatIndicator (e.g., ifsingle PMI reporting is configured, a single PMI may be reported for theentire CSI reporting band. If multiple PMI reporting is configured witha number of antenna ports that is different from 2 antenna ports, asingle wideband indication may be reported for the entire CSI reportingband and one subband indication may be reported for each subband in theCSI reporting band. If multiple PMIs are configured with 2 antennaports, a PMI may be reported for each subband in the CSI reportingband).

A wireless device may be configured with CSIReportQuantity to report oneor more parameters, for example, if the wireless device is configuredwith higher layer parameter CodebookType set to ‘TypeI-SinglePanel’ andPMI-FormatIndicator is configured for single PMI reporting. The one ormore parameters may comprise at least one of the following: RI/CRI and aPMI comprising a single wideband indication for the entire CSI reportingband; and/or RI/CRI, CQI, and/or a PMI comprising a single widebandindication for the entire CSI reporting band. The CQI may be calculatedassuming PDSCH transmission with precoders. The wireless device mayassume that one precoder may be randomly selected from the set of N_(p)precoders for each PRG on PDSCH. The PRG size for CQI calculation may beconfigured by the higher layer parameter PUSCH-bundle-size-for-CSI.

A wireless device may report CSI, for example, if the wireless device isconfigured with semi-persistent CSI reporting and if both CSI-IM andnon-zero power CSI-RS resources are configured as periodic orsemi-persistent. A wireless device may report CSI, for example, if thewireless device is configured with aperiodic CSI reporting and if bothCSI-IM and non-zero power CSI-RS resources are configured as periodic,semi-persistent, or aperiodic.

A trigger state configured using the higher layer parameterReportTrigger may be associated with one or more ReportConfig. One ofthe one or more ReportConfig may be linked to periodic, semi-persistent,or aperiodic resource setting(s). For example, the resource setting maybe for channel measurement for L1-RSRP computation, for example, if oneresource setting is configured. A first resource setting may be forchannel measurement and a second resource setting may be forinterference measurement performed on CSI-IM or on non-zero powerCSI-RS, for example, if two resource settings are configured. A firstresource setting may be for channel measurement, a second resourcesetting may be for CSI-IM based interference measurement, and a thirdresource setting may be for non-zero power CSI-RS based interferencemeasurement, for example, if three resource settings are configured.

For CSI measurement(s), a wireless device may assume a non-zero powerCSI-RS port configured for interference measurement corresponding to aninterference transmission layer; one or more interference transmissionlayers on non-zero power CSI-RS ports for interference measurement(taking into account the associated EPRE ratios); and/or otherinterference signal on REs of non-zero power CSI-RS resource for channelmeasurement, non-zero power CSI-RS resource for interferencemeasurement, and/or CSI-IM resource for interference measurement.

A wireless device may be configured with higher layer parameterNon-PMI-PortIndication in a ReportConfig, for example, if the wirelessdevice is configured with the higher layer parameter ReportQuantity setto ‘CRI/RI/CQI.’ r ports may be indicated in the order of layer orderingfor rank r and each CSI-RS resource in the CSI resource setting linkedto the ReportConfig in a MeasLinkConfig, based on the order of theassociated NZP-CSI-RS-ResourceConfigID in the linked CSI resourcesetting linked for channel measurement. A wireless device may use theports indicated for that rank for the selected CSI-RS resource, forexample, if the wireless device is configured with the higher layerparameter ReportQuantity set to ‘CRI/RI/CQI’ for calculating the CQI fora rank. The precoder for the indicated ports may be assumed to be theidentity matrix.

For Resource Sets configured with the higher layer parameterResourceConfigType set to ‘aperiodic’, trigger states for ReportingSetting(s) and/or Resource Set(s) for channel and/or interferencemeasurement on one or more component carriers may be configured usingthe higher layer parameter AperiodicReportTrigger. For aperiodic CSIreport triggering, a single set of one or more CSI triggering states maybe higher layer configured. The CSI triggering states may be associatedwith a candidate DL BWP. A wireless device may not be expected to betriggered with a CSI report for a non-active DL BWP. A trigger state maybe initiated using the DCI CSI request field.

No CSI may be requested, for example, if the value of the DCI CSIrequest field is zero. The wireless device may receive a selectioncommand, via MAC CE, used to map up to 2^(N) ^(TS) −1 trigger states tothe codepoints of the DCI CSI request field, for example, if the numberof configured CSI triggering states in AperiodicReportTrigger is greaterthan 2^(N) ^(TS) −1. N_(TS) may be the number of bits in the DCI CSIrequest field. N_(TS) may be configured by the higher layer parameterReportTriggerSize and N_(TS) may be one of values from the set {0, 1, 2,3, 4, 5, 6} (e.g., N_(TS)∈{0,1,2,3,4,5,6}). The DCI CSI request fieldmay directly indicate the triggering state and the wireless device'squasi-colocation assumption, for example, if the number of CSItriggering states in AperiodicReportTrigger is less than or equal to2^(N) ^(TS) −1. For an aperiodic CSI-RS resource associated with a CSItriggering state, the wireless device may be indicated the quasico-location configuration of quasi co-location RS source(s) and quasico-location type(s) through higher layer signaling ofQCL-Info-aPerodicReportingTrigger, which may comprise a list ofreferences to TCI-RS-SetConfig's for the aperiodic CSI-RS resourcesassociated with the CSI triggering state. If a TCI-RS-SetConfig in thelist is configured with a reference to an RS associated with QCL-TypeD,that RS may be an SS/PBCH block or a CSI-RS resource configured asperiodic or semi-persistent.

For a wireless device configured with the higher layer parameterAperiodicReportTrigger, for example, if a resource setting linked to aReportConfig has multiple aperiodic resource sets and a subset of theaperiodic resource sets is associated with the trigger state, a higherlayer configured bitmap ResourceSetBitmap may be configured per triggerstate per resource setting to select the CSI-IM/NZP CSI-RS resourceset(s) from the resource setting. The CSI-RS offset may be configuredper resource set in the higher layer parameterAperiodicNZP-CSI-RS-TriggeringOffset, for example, if aperiodic CSI-RSis used with aperiodic reporting. The CSI-RS triggering a first offset(e.g., offset X) may be measured in slots.

For semi-persistent reporting on a PUSCH, a set of semi-persistent CSIreport settings may be configured by higher layer(s) (e.g.,semi-statically configured by RRC). For example, the set ofsemi-persistent CSI report setting may be configured bySemi-persistent-on-PUSCHReportTrigger, and the CSI request field in aDCI scrambled with a particular RNTI (e.g., SP-CSI C-RNTI) may activateat least one of the semi-persistent CSI reports.

For semi-persistent reporting on a PUCCH, a set of semi-persistent CSIreport settings may be configured by higher layer(s) (e.g.,semi-statically configured by RRC). For example, the set ofsemi-persistent CSI report settings may be configured byreportConfigType with the PUCCH resource for transmitting the CSIreport. Semi-persistent reporting on a PUCCH may be activated by anactivation command transmitted via a DCI and/or a MAC CE. The activationcommand may select at least one of the semi-persistent CSI Reportsettings for use by the wireless device on the PUCCH. The wirelessdevice may (or shall) report the CSI on PUSCH, for example, if the fieldreportConfigType is not present.

A wireless device may be configured with the higher layer parameterResourceConfigType set to ‘semi-persistent.’ If a wireless devicereceives an activation command via a MAC CE and/or a DCI for CSI-RSresource(s) for channel measurement and CSI-IM/NZP CSI-RS resource(s)for interference measurement associated with configured CSI resourcesetting(s) in slot n, the corresponding actions and the assumptions, forthe wireless device, (including quasi-co-location assumptions providedby a reference to a TCI-RS-SetConfig) on CSI-RS/CSI-IM transmissioncorresponding to the configured CSI-RS/CSI-IM resource configuration(s)may be used, for example, no later than the minimum requirement (e.g.,defined in NR specifications). If a wireless device receives adeactivation command via a MAC CE and/or a DCI for activatedCSI-RS/CSI-IM resource(s) associated with configured CSI resourcesetting(s) in slot n, the corresponding actions and assumption, for thewireless device, on cessation of CSI-RS/CSI-IM transmissioncorresponding to the deactivated CSI-RS/CSI-IM resource(s) may be used,for example, no later than the minimum requirement (e.g., defined in NRspecifications). The wireless device may assume that the CSI-RSresource(s) for channel measurement and the CSI-IM/NZP CSI-RSresource(s) for interference measurement are spatially quasi co-located.

A wireless device may perform aperiodic CSI reporting using a PUSCH inslot n+Y on a cell c upon successful decoding in slot n of an uplink DCIformat for a cell c. Y may be indicated in the decoded uplink DCI. Thehigher layer parameter AperiodicReportSlotOffset may comprise theallowed values for Y for a given Reporting Setting. Y_(i,j) may bedefined as the ith allowed value for Report Setting j (j=0, . . . ,N_(Rep)−1), for example, if N_(Rep)≥1 reports are scheduled. The ithcodepoint of the DCI field may correspond to the allowed value

$Y_{i} = {\max\limits_{j}{Y_{i,j}.}}$

An aperiodic CSI report carried on the PUSCH may support wideband,partial band, and/or sub-band frequency granularities. An aperiodic CSIreport carried on the PUSCH may support Type I and Type II CSI.

A wireless device may perform semi-persistent CSI reporting on the PUSCHupon a successful decoding of an uplink DCI format. The uplink DCIformat may comprise one or more CSI Reporting Setting Indications. Theassociated CSI Measurement Links and CSI Resource Settings may beconfigured by higher layer(s). Semi-persistent CSI reporting on thePUSCH may support Type I and Type II CSI with wideband, partial band,and/or sub-band frequency granularities. The PUSCH resources and MCS maybe allocated semi-persistently by an uplink DCI.

CSI reporting on PUSCH may be multiplexed with uplink data on PUSCH. CSIreporting on PUSCH may be performed without any multiplexing with uplinkdata from the wireless device.

Type I CSI feedback may be supported for CSI Reporting on a PUSCH. TypeI subband CSI may be supported for CSI Reporting on the PUSCH. Type IICSI may be supported for CSI Reporting on the PUSCH. For Type I CSIfeedback on the PUSCH, a CSI report may comprise at least two parts,Part 1 and Part 2. For example, Part 1 may comprise RI/CRI and CQI forthe first codeword. Part 2 may comprise PMI and may comprise the CQI forthe second codeword, for example, if RI>4.

For Type II CSI feedback on the PUSCH, a CSI report may comprise atleast two parts, Part 1 and Part 2. Part 1 may be used to identify thenumber of information bits in Part 2. Part 1 may be transmitted in itsentirety before Part 2. Part 1 may have a fixed payload size and maycomprise RI, CQI, and an indication of the number of non-zero widebandamplitude coefficients per layer for the Type II CSI. The fields of Part1—RI, CQI, and the indication of the number of non-zero widebandamplitude coefficients for each layer—may be separately encoded. Part 2may comprise the PMI of the Type II CSI. Part 1 and Part 2 may beseparately encoded. A Type II CSI report that may be carried on thePUSCH may be computed independently from any Type II CSI report that maybe carried on the Long PUCCH.

The CSI feedback may comprise at least one part, for example, if thehigher layer parameter ReportQuantity is configured with one of thevalues ‘CRI/RSRP’ or ‘SSBRI/RSRP.’

The wireless device may omit a portion of the Part 2 CSI, for example,if CSI reporting on the PUSCH comprises two parts. Omission of Part 2CSI may be based on a priority order.

FIG. 19 shows an example priority order associated with one or more CSIreports. N_(Rep) may be the number of CSI reports in one slot. Priority0 may be the highest priority and priority 2N_(Rep) (and/or 2N_(Rep)−1)may be the lowest priority, and the CSI report numbers may correspond tothe order of the associated ReportConfigID. If Part 2 CSI informationfor a particular priority level is omitted, the wireless device may omitone or more (or all) pieces of the information at that priority level.

Part 2 CSI may be omitted, for example, if a CSI is multiplexed with aUL-SCH on a PUSCH and if the UCI code rate for transmitting one or moreof Part 2 is greater than a threshold code rate c_(T). For example

$c_{T} = {\frac{c_{MCS}}{\beta_{offset}^{{CSI} - 2}} \cdot c_{MCS}}$

may be a target PUSCH code rate and β_(offset) ^(CSI-2) may be the CSIoffset value. Part 2 CSI may be omitted level by level beginning withthe lowest priority level until the lowest priority level may bereached, which may cause the UCI code rate to be less than or equal toc_(T).

A wireless device may be semi-statically configured by higher layer(s)to perform periodic CSI Reporting on the PUCCH. A wireless device may beconfigured by higher layer(s) for one or more periodic CSI Reportscorresponding to one or more higher-layer-configured CSI ReportingSetting Indications. The associated CSI Measurement Links and CSIResource Settings may be configured by higher layer(s). Periodic CSIreporting on the short and the long PUCCH may support wideband andpartial band frequency granularities. Periodic CSI reporting on thePUCCH may support Type I CSI.

A wireless device may perform semi-persistent CSI reporting on the PUCCHupon a successful decoding of a selection command transmitted via a MACCE and/or a DCI. The selection command may comprise one or more CSIreporting setting indications. The associated CSI measurement links andCSI resource settings may be configured (e.g., semi-staticallyconfigured by RRC). Semi-persistent CSI reporting on the PUCCH maysupport Type I CSI. Semi-persistent CSI reporting on the short PUCCH maysupport Type I CSI with wideband and partial band frequencygranularities. Semi-persistent CSI reporting on the long PUCCH maysupport Type I subband CSI and Type I CSI with wideband and partial bandfrequency granularities.

Periodic CSI reporting on the short and long PUCCH may support widebandand partial band frequency granularities. Periodic CSI reporting on thePUCCH may support Type I CSI. The CSI payload carried by the short PUCCHand long PUCCH may be identical to each other, irrespective of RI/CRI,for example, if the short and long PUCCH carry Type I CSI with widebandand partial band frequency granularity. For Type I CSI sub-bandreporting on the long PUCCH, the payload may be split into at least twoparts. The first part may comprise RI/CRI and/or CQI for the firstcodeword. The second part may comprise PMI and/or the CQI for the secondcodeword, for example, if RI>4.

A periodic report (e.g., a periodic CSI report) carried on the longPUCCH may support Type II CSI feedback (e.g., Part 1 of Type II CSIfeedback). A semi-persistent report (e.g., a semi-persistent CSI report)carried on the Long PUCCH may support Type II CSI feedback (e.g., Part 1of Type II CSI feedback). Supporting Type II CSI reporting on the LongPUCCH may be a device capability (e.g., a UE capability). A Type II CSIreport (e.g., Part 1) carried on the Long PUCCH may be calculatedindependently (e.g., regardless of one of Type II CSI reports carried onthe PUSCH).

A base station may transmit one or more RRC messages comprising one ormore CSI configuration parameters. The one or more CSI configurationparameters may comprise at least one of: one or more CSI-RS resourcesettings; one or more CSI reporting settings; and/or one or more CSImeasurement settings.

A CSI-RS resource setting may comprise one or more CSI-RS resource sets.There may be at least one CSI-RS resource set for a periodic CSI-RSand/or a SP CSI-RS.

A CSI-RS resource set may comprise parameters indicating at least oneof: a CSI-RS type (e.g., periodic, aperiodic, semi-persistent); one ormore CSI-RS resources comprising at least one of CSI-RS resourceconfiguration identity, number of CSI-RS ports, at least one CSI RSconfiguration (e.g., symbol and RE locations in a mini-slot, slot,and/or subframe), and/or at least one CSI-RS mini-slot, slot or subframeconfiguration (e.g., mini-slot, slot or subframe location, offset andperiodicity in radio mini-slot, slot, subframe, or frame); at least oneCSI-RS power parameter; at least one CSI-RS sequence parameter; at leastone CDM type parameter; at least one frequency density; at least onetransmission comb; and/or at least one QCL parameter.

A CSI-RS transmission may be periodic, aperiodic, or semi-persistent.For a periodic transmission, the configured CSI-RS may be transmittedusing a configured periodicity in time domain. For an aperiodictransmission, the configured CSI-RS may be transmitted in a particulartime slot or subframe (e.g., the time slot or subframe may be dedicatedand/or scheduled dynamically via UL grants). For a semi-persistenttransmission, one or more configured CSI-RS may be transmittedsemi-persistently, for example, if activated by a CSI activation MAC CEor DCI. The transmission of the one or more configured CSI-RS may bestopped, for example, if deactivated by a CSI deactivation MAC CE orDCI. The transmission of the one or more configured CSI-RS may bestopped, for example, if a particular timer (if configured) expires. Thetimer (e.g., a CSI activation timer) may start, for example, after or inresponse to receiving the CSI activation MAC CE or DCI.

A CSI reporting setting may comprise at least one of: at least onereport configuration identifier; at least one report type; one or morereported CSI parameter(s); one or more CSI Type (I or II); one or morecodebook configuration parameters; a report quantity indicatorindicating CSI-related or L1-RSRP-related quantities to report; one ormore parameters indicating time-domain behavior; frequency granularityfor CQI and PMI; and/or measurement restriction configurations. Thereport type may indicate a time domain behavior of the report(aperiodic, semi-persistent, or periodic). Each of the one or more CSIreporting settings may further comprise at least one of: one periodicityparameter; one duration parameter; and/or one offset (e.g., in unit ofslots), for example, if the report type is a periodic or semi-persistentreport. The periodicity parameter may indicate the periodicity of a CSIreport. The duration parameter may indicate the duration of a CSI reporttransmission. The offset parameter may indicate a value of a timingoffset of a CSI report from a reference time.

A CSI measurement setting may comprise one or more links comprising oneor more link parameters. The one or more link parameters may comprise atleast one of: one CSI reporting setting indication; CSI-RS resourcesetting indication; and/or one or more measurement parameters.

A base station may trigger a CSI reporting by transmitting an RRCmessage, a MAC CE, and/or a DCI. A wireless device may transmit one ormore semi-persistent (SP) CSI report on a PUCCH, with a transmissionperiodicity, for example, after or in response to receiving a MAC CE (ora DCI) activating a SP CSI reporting. A wireless device may transmit oneor more SP CSI report on a PUSCH, for example, after or in response toreceiving a MAC CE (or a DCI) activating a SP CSI reporting.

FIG. 20 shows an example of SP CSI configuration with a messageactivating SP CSI and a message deactivating SP CSI. A base station maytransmit, to a wireless device, an RRC configuration message 2011. Basedon the RRC configuration message, for example, SP CSI-RS configurationand/or SP CSI report settings may be configured for the wireless device.The base station may transmit, to the wireless device and in a slot(mini-slot, or subframe) n, an indication of activating SP CSI 2021(e.g., a MAC CE or DCI for activating SP CSI reporting). The basestation may configure an offset k 2030 between the indication ofactivating SP CSI 2021 and the first transmission of CSI-RS. The basestation may transmit, to the wireless device, the value of the offset k2030. The offset k 2030 may be k number of TTIs (e.g., k mini-slots,slots, or subframes). The wireless device may monitor for one or moreCSI-RS transmissions (e.g., the first CSI-RS transmission 2030 and oneor more subsequent CSI-RS transmissions 2032). The base station maystart transmitting one or more SP CSI-RSs 2031, 2032, for example, aftertransmitting the indication of activating SP CSI 2021 in the slot(mini-slot, or subframe) n. For example, the base station may transmitthe first SP CSI-RS 2031 in a TTI (mini-slot, slot, or subframe) n+kwith the offset k 2030. k may be predefined (e.g., k=0) and/or may besemi-statically configured by an RRC message. The wireless device maytransmit SP CSI reports (e.g., SP-CSI reports 2051, 2052, 2053, 2054) inTTIs (mini-slot, slot, or subframe) n+k+m, n+k+m+l, n+k+m+2*l,n+k+m+3*l, etc., with a periodicity of l TTIs (mini-slots, slots, orsubframes). The wireless device may stop transmitting SP CSI reporting,for example, after or in response to receiving an indication ofdeactivating SP CSI 2022 (e.g., a MAC CE or DCI for deactivating SP CSIreporting).

One or more power control mechanisms may be used for transmitting one ormore wireless signals. Some example parameters may be used for the oneor more power control mechanisms. One or more example power controlprocesses may be implemented in technologies such as LTE, LTE Advanced,New Radio (e.g., 5G), and/or any other technologies. A radio technologymay have its own specific parameters. Various power control mechanismsmay be similarly or differently implemented in different radio systems.For example, a radio system may enhance physical layer power controlmechanisms, for example, if some layer 2 parameters are taken intoaccount.

For a downlink power control, a base station (or other devices) maydetermine the Energy Per Resource Element (EPRE). The term resourceelement energy may denote the energy prior to CP insertion. The termresource element energy may denote the average energy taken over allconstellation points for the modulation scheme used. For an uplink powercontrol, a wireless device and/or a base station (or other devices) maydetermine the average power over an SC-FDMA symbol in which the physicalchannel may be transmitted.

A wireless device may follow the procedures for PUSCH and SRS, forexample, if the wireless device is configured with an LAA SCell foruplink transmissions. It may be assumed that a frame structure type 1for the LAA SCell is used unless stated otherwise.

For a PUSCH, the transmit power {circumflex over (P)}_(PUSCH,c)(i), maybe first scaled by the ratio of the number of antennas ports with anon-zero PUSCH transmission to the number of configured antenna portsfor the transmission scheme. The resulting scaled power may be splitequally across the antenna ports on which the non-zero PUSCH istransmitted. For a PUCCH or SRS, the transmit power {circumflex over(P)}_(PUCCH)(i), or {circumflex over (P)}_(SRS,c)(i) may be splitequally across the configured antenna ports for the PUCCH or SRS.{circumflex over (P)}_(PUSCH,c)(i) {circumflex over (P)}_(PUCCH)(i), and{circumflex over (P)}_(SRS,c)(i) may be the linear values ofP_(PUSCH,c)(i) P_(PUCCH)(i), and P_(SRS,c)(i), respectively.P_(PUSCH,f,c)(i) P_(PUCCH,f,c)(i), and P_(SRS,f,c)(i) may be thetransmit power of a PUSCH, PUCCH, SRS on carrier f of a cell c,respectively. {circumflex over (P)}_(PUSCH,f,c)(i) {circumflex over(P)}_(PUCCH,f,c)(i), and {circumflex over (P)}_(SRS,f,c)(i) may be thelinear values of P_(PUSCH,f,c)(i) P_(PUCCH,f,c)(i), and P_(SRS,f,c)(i),respectively. P_(PUSCH,c)(i) P_(PUCCH)(i), and P_(SRS,c)(i) may beinterchangeable with P_(PUSCH,f,c)(i) P_(PUCCH,f,c)(i), andP_(SRS,f,c)(i), respectively, for example, if the cell c has a singlecarrier and/or if no confusion exists on a carrier index. {circumflexover (P)}_(PUSCH,c)(i) {circumflex over (P)}_(PUCCH,c)(i), and{circumflex over (P)}_(SRS,c)(i) may be interchangeable with {circumflexover (P)}_(PUSCH,f,c)(i) {circumflex over (P)}_(PUCCH,f,c)(i), and{circumflex over (P)}_(SRS,f,c)(i), respectively, for example, if thecell c has a single carrier and/or if no confusion exists on a carrierindex. A cell wide overload indicator (OI) and a High InterferenceIndicator (HII) to control UL interference may be parameters in aspecification (e.g., in LTE and/or NR technologies specifications).

A wireless device may follow the procedures for both MCG and SCG, forexample, if the wireless device is configured with an SCG. If theprocedures are used for an MCG, the terms ‘secondary cell,’ ‘secondarycells,’ ‘serving cell,’ ‘serving cells’ may refer to secondary cell,secondary cells, serving cell, serving cells belonging to the MCG,respectively. The term ‘primary cell’ may refer to the PCell of the MCG.If the procedures are used for an SCG, the terms ‘secondary cell,’‘secondary cells,’ ‘serving cell,’ ‘serving cells’ may refer tosecondary cell, secondary cells (not including PSCell), serving cell,serving cells belonging to the SCG, respectively. The term ‘primarycell’ may refer to the PSCell of the SCG.

A wireless device may follow the procedures for a primary PUCCH group, asecondary PUCCH group, or both the primary PUCCH group and the secondaryPUCCH group, for example, if the wireless device is configured with aPUCCH-SCell. If the procedures are used for a primary PUCCH group, theterms ‘secondary cell,’ ‘secondary cells,’ ‘serving cell,’ ‘servingcells’ may refer to secondary cell, secondary cells, serving cell,serving cells belonging to the primary PUCCH group, respectively. If theprocedures are used for a secondary PUCCH group, the terms ‘secondarycell,’ ‘secondary cells,’ ‘serving cell,’ ‘serving cells’ may refer tosecondary cell, secondary cells, serving cell, serving cells belongingto the secondary PUCCH group, respectively.

A wireless device's transmit power P_(PUSCH,c)(i) for a PUSCHtransmission in subframe (TTI, slot, and/or mini-slot) i for the servingcell c may be given by

${{P_{{PUSCH},c}(i)} = {\min {\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\; \_ \; {PUSCH}},c}(j)} +} \\{{{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}},$

for example, if the wireless device transmits the PUSCH without asimultaneous PUCCH on a carrier f of the serving cell c.

A wireless device's transmit power P_(PUSCH,c)(i) for a PUSCHtransmission in subframe (TTI, slot, and/or mini-slot) i for the servingcell c may be given by

${{P_{{PUSCH},c}(i)} = {\min {\begin{Bmatrix}{{10{\log_{10}\left( {{{\hat{P}}_{{CMAX},c}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)}},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\; \_ \; {PUSCH}},c}(j)} +} \\{{{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}},$

for example, if the wireless device transmits the PUSCH simultaneouswith a PUCCH on a carrier f of the serving cell c and/or the PUSCHtransmission at least partially overlaps with the PUCCH transmission.

A wireless device may assume that the wireless device's transmit powerP_(PUSCH,c)(i) for the PUSCH transmission in subframe (TTI, slot, and/ormini-slot) i for the serving cell c may be computed by

P _(PUSCH,c)(i)=min {P _(CMAX,c)(i),P _(O) _(_)_(PUSCH,c)(1)+α_(c)(1)·PL _(c) +f _(c)(i)} [dBm],

for example, if the wireless device is not transmitting PUSCH for theserving cell c, for the accumulation of TPC command received with a DCI(e.g., DCI format 3/3A and/or format 2_2) for the PUSCH.

One or more example parameters for P_(PUSCH,c)(i) are described below.

P_(CMAX,c)(i) may be the configured transmit power, of the wirelessdevice, in a subframe (TTI, slot, and/or mini-slot) i for a serving cellc, and {circumflex over (P)}_(CMAX,c)(i) may be the linear value ofP_(CMAX,c)(i). The wireless device may assume P_(CMAX,c)(i), forexample, if the wireless device transmits a PUCCH without a PUSCH in thesubframe (TTI, slot, and/or mini-slot) i for the serving cell c, for theaccumulation of a TPC command received with a DCI format (e.g., DCIformat 3/3A and/or format 2_2) for the PUSCH. The wireless device maydetermine P_(CMAX,c)(i) assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dB andΔT_(C)=0 dB, for example, if the wireless device does not transmit aPUCCH and a PUSCH in a subframe (TTI, slot, and/or mini-slot) i for theserving cell c, for the accumulation of TPC command received with a DCIformat (e.g., DCI format 3/3A or format 2_2) for the PUSCH. The MPR,A-MPR, P-MPR and ΔT_(C) may be pre-defined in a specification (e.g., inLTE, NR, and/or any other technologies specifications).

{circumflex over (P)}_(PUCCH)(i) may be the linear value ofP_(PUCCH)(i).

M_(PUSCH,c)(i) may be the bandwidth of the PUSCH resource assignmentexpressed in a number of resource blocks valid for a subframe (TTI,slot, and/or mini-slot) i and a serving cell c. M_(PUSCH,c)(i) may beprovided by an uplink grant transmitted by the base station.

If, for example, the wireless device is configured with a higher layerparameter (e.g., UplinkPowerControlDedicated) for a serving cell c andif, for example, a subframe (TTI, slot, and/or mini-slot) i belongs toan uplink power control subframe (TTI, slot, and/or mini-slot) set 2 asindicated by the higher layer parameter (e.g., tpc-SubframeSet),

-   -   if j=0, the wireless device may set P_(O) _(_)        _(PUSCH,c)(0)=P_(O) _(_) _(UE) _(_) _(PUSCH,c,2)(0)+P_(O) _(_)        _(NOMINAL) _(_) _(PUSCH,c,2)(0), where j=0 may be used for PUSCH        (re)transmissions corresponding to a semi-persistent (configured        and/or grant-free) grant. P_(O) _(_) _(UE) _(_) _(PUSCH,c,2)(0)        and P_(O) _(_) _(NOMINAL) _(_) _(PUSCH,c,2)(0) may be the        parameters provided by higher layers, for example,        p0-UE-PUSCH-Persistent-SubframeSet2 and        p0-NominalPUSCH-Persistent-SubframeSet2, for each serving cell        c.    -   if j=1, the wireless device may set P_(O) _(_)        _(PUSCH,c)(1)=P_(O) _(_) _(UE) _(_) _(PUSCH,c,2)(1)+P_(O) _(_)        _(NOMINAL) _(_) _(PUSCH,c,2)(1), where j=1 may be used for PUSCH        (re)transmissions corresponding to a dynamic scheduled grant.        P_(O) _(_) _(UE) _(_) _(PUSCH,c,2)(1) and P_(O) _(_) _(NOMINAL)        _(_) _(PUSCH,c,2)(1) may be the parameters provided by higher        layers, for example, p0-UE-PUSCH-SubframeSet2 and        p0-NominalPUSCH-SubframeSet2 respectively, for the serving cell        c.    -   if j=2, the wireless device may set P_(O) _(_)        _(PUSCH,c)(2)=P_(O) _(_) _(UE) _(_) _(PUSCH,c)(2)+P_(O) _(_)        _(NOMLNAL) _(_) _(PUSCH,c)(2) where P_(O) _(_) _(UE) _(_)        _(PUSCH,c)(2)=0 and P_(O) _(_) _(NOMINAL) _(_)        _(PUSCH,c)(2)=P_(O) _(_) _(PRE)+Δ_(PREAMBLE) _(_) _(Msg3), where        the parameter preambleInitialReceivedTargetPower (P_(O) _(_)        _(PRE)) and Δ_(PREAMBLE) _(_) _(Msg3) may be signaled from        higher layers for the serving cell c, where j=2 may be used for        PUSCH (re)transmissions corresponding to the random access        response grant. Otherwise, P_(O) _(_) _(PUSCH,c)(j) may be a        parameter comprising the sum of a component P_(O) _(_)        _(NOMINAL) _(_) _(PUSCH,c)(j) provided from higher layers for        j=0 and 1 and a component P_(O) _(_) _(UE) _(_) _(PUSCH,c)(j)        provided by higher layers for j=0 and 1 for the serving cell c.        For PUSCH (re)transmissions corresponding to a semi-persistent        (configured and/or grant-free) grant, for example, j=0; for        PUSCH (re)transmissions corresponding to a dynamic scheduled        grant, for example, j=1; and for PUSCH (re)transmissions        corresponding to the random access response grant, for example,        j=2. P_(O) _(_) _(UE) _(_) _(PUSCH,c)(2)=0 and P_(O) _(_)        _(NOMINAL) _(_) _(PUSCH,c)(2)=P_(O) _(_) _(PRE)+Δ_(PREAMBLE)        _(_) _(Msg3), where the parameter        preambleInitialReceivedTargetPower (P_(O) _(_) _(PRE)) and        Δ_(PREAMBLE) _(_) _(Msg3) may be signaled from higher layers for        serving cell c.

If, for example, the wireless device is configured with a higher layerparameter (e.g., UplinkPowerControlDedicated) for serving cell c, andif, for example, a subframe (TTI, slot, and/or mini-slot) i belongs toan uplink power control subframe (TTI, slot, and/or mini-slot) set 2 asindicated by the higher layer parameter (e.g., tpc-SubframeSet),

-   -   For j=0 or 1, the wireless device may set        α_(c)(j)=α_(c,2)ε{0,0.4,0.5,0.6,0.7,0.8,0.9,1}. α_(c,2) may be        the parameter alpha-SubframeSet2 provided by higher layers for        each serving cell c.    -   For j=2, the wireless device may set α_(c)(j)=1. Otherwise, for        j=0 or 1, α_(c)∈{0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1} may be a        3-bit parameter provided by higher layers for the serving        cell c. For j=2, the wireless device may set α_(c)(j)=1.

PL_(c) may be the downlink path loss estimate calculated in the wirelessdevice for the serving cell c (e.g., in dB) andPL_(c)=referenceSignalPower higher layer filtered RSRP, wherereferenceSignalPower may be provided by higher layers and RSRP may bedefined for the reference serving cell, and the higher layer filterconfiguration may be defined for the reference serving cell. For theuplink of the primary cell, the primary cell may be used as thereference serving cell for determining referenceSignalPower and higherlayer filtered RSRP, for example, if the serving cell c belongs to a TAGcontaining the primary cell. For the uplink of the secondary cell, theserving cell configured by the higher layer parameterpathlossReferenceLinking may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP. For theuplink of the PSCell, the PSCell may be used as the reference servingcell for determining referenceSignalPower and higher layer filteredRSRP, for example, if the serving cell c belongs to a TAG containing thePSCell. For the uplink of the secondary cell other than PSCell, theserving cell configured by the higher layer parameterpathlossReferenceLinking may be used as the reference serving cell fordetermining referenceSignalPower and higher layer filtered RSRP, forexample, if the serving cell c belongs to a TAG containing the PSCell.Serving cell c may be used as the reference serving cell for determiningreferenceSignalPower and higher layer filtered RSRP, for example, if theserving cell c belongs to a TAG not containing the primary cell orPSCell. The downlink path loss may be calculated by measuring one ormore reference signals (e.g., CSI-RSs and/or synchronization signalstransmitted from the base station).

A wireless device may set Δ_(TF,c)(i)=10 log₁₀((2^(BPRE·K) ^(s)−1)·β_(offset) ^(PUSCH)) for K_(s)=1.25 and 0 for K_(s)=0 where K_(s)may be given by the parameter (e.g., deltaMCS-Enabled) provided byhigher layers for each serving cell c. BPRE and β_(offset) ^(PUSCH), foreach serving cell c, may be computed as below. K_(s)=0 may be fortransmission mode 2.

-   -   BPRE=O_(CQI)/N_(RE) may be for control data (e.g.,        periodic/aperiodic CSI, and/or SP CSI) sent via a PUSCH without        UL-SCH data and

$\sum\limits_{r = 0}^{C - 1}{K_{r}/N_{RE}}$

-   -    for other cases. C may be the number of code blocks, K_(r) may        be the size for code block r, O_(CQI) may be the number of        CQI/PMI bits including CRC bits and N_(RE) may be the number of        resource elements determined as N_(RE)=M_(sc)        ^(PUSCH-initial)·N_(symb) ^(PUSCH-initial), where C, K_(r),        M_(sc) ^(PUSCH-initial) and N_(symb) ^(PUSCH-initial) may be        pre-defined in a specification (e.g., the LTE, NR, and/or any        other technology specifications).    -   β_(offset) ^(PUSCH)=β_(offset) ^(CQI), which may be for control        data (e.g., periodic/aperiodic CSI, and/or SP CSI) sent via a        PUSCH without UL-SCH data and 1 for other cases.

δ_(PUSCH,c) may be a correction value (e.g., one or more correctionvalues described herein), which may be a TPC command, and/or may beincluded in a PDCCH/EPDCCH with a DCI format (e.g., DCI format0/0A/0B/4/4A/4B in LTE and/or DCI format 0_0/0_1 in NR) or in an MPDCCHwith a DCI format (e.g., 6-0A) for a serving cell c or jointly codedwith other TPC commands in a PDCCH/MPDCCH with a DCI format (e.g., DCIformat 3/3A in LTE and/or DCI format 2_2 in NR) of which CRC parity bitsmay be scrambled with a group RNTI (e.g, TPC-PUSCH-RNTI). The currentPUSCH power control adjustment state for serving cell c may be given byf_(c,2)(i), and the wireless device may use f_(c,2)(i) instead off_(c)(i) to determine P_(PUSCH,c)(i), for example, if the wirelessdevice is configured with a higher layer parameter (e.g.,UplinkPowerControlDedicated) for the serving cell c and if a subframe(TTI, slot, and/or mini-slot) i belongs to an uplink power controlsubframe (e.g., TTI, slot, and/or mini-slot) set 2 as indicated by thehigher layer parameter (e.g., tpc-SubframeSet). Otherwise, the currentPUSCH power control adjustment state for the serving cell c may be givenby f_(c)(i) f_(c,2)(i) and f_(c)(i) may be defined by:

-   -   f_(c)(i)=f_(c)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH)) and        f_(c,2)(i)=f_(c,2)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH)), for example,        if accumulation may be enabled based on the parameter (e.g.,        Accumulation-enabled) provided by higher layers and/or if the        TPC command δ_(PUSCH,c) may be included in a PDCCH/EPDCCH with a        DCI format (e.g., DCI format 0 in LTE and/or DCI format 0_0 in        NR) or in an MPDCCH with a DCI format (e.g., DCI format 6-0A)        for the serving cell c where the CRC may be scrambled by the        Temporary C-RNTI. δ_(PUSCH,c)(i−K_(PUSCH)) may be signaled on a        PDCCH/EPDCCH with a DCI format (e.g., DCI format 0/0A/0B/4/4A/4B        in LTE and/or DCI format 0_0/0_1 in NR) or an MPDCCH with a DCI        format (e.g., 6-0A) or a PDCCH/MPDCCH with a DCI format (e.g.,        DCI format 3/3A in LTE and/or DCI format 2_2 in NR) on subframe        (TTI, slot, and/or mini-slot) i−K_(PUSCH), and where f_(c)(0)        may be the first value after reset of accumulation.

For a wireless device (e.g., a band-limited (BL)/coverage enhancement(CE)CE wireless device configured with CEModeA), a subframe (TTI, slot,and/or mini-slot) i−K_(PUSCH) may be the last subframe (TTI, slot,and/or mini-slot) in which the MPDCCH with a DCI format (e.g., 6-0A) orMPDCCH with a DCI format (e.g., 3/3A) may be transmitted.

The value of K_(PUSCH) may be,

for FDD or FDD-TDD and serving cell frame structure type 1, K_(PUSCH)=4;for TDD, if the wireless device is configured with more than one servingcell and the TDD UL/DL configuration of at least two configured servingcells are not the same, or if the wireless device is configured with theparameter (e.g., EIMTA-MainConfigServCell) for at least one servingcell, or for FDD-TDD and serving cell frame structure type 2, the “TDDUL/DL configuration” may refer to the UL-reference UL/DL configurationfor the serving cell c;for a TDD UL/DL configurations (e.g., configuration 1-6 in LTE),K_(PUSCH) may be given in a predefined table in a specification (e.g.,LTE and/or NR specifications); for a TDD UL/DL configuration (e.g.,configuration 0 in LTE), for example, if the PUSCH transmission in afirst subframe (TTI, slot, and/or mini-slot) or a second subframe (TTI,slot, and/or mini-slot) (e.g., 7) may be scheduled with a PDCCH/EPDCCHof a DCI format (e.g., 0/4), or an MPDCCH of a DCI format (e.g., DCIformat 6-0A in LTE), in which the least significant bit (LSB) of the ULindex may be set to 1, K_(PUSCH)=7, and for all other PUSCHtransmissions, K_(PUSCH) may be given in a predefined table (e.g., inLTE and/or NR specifications);for TDD UL/DL configurations 0-5 and a wireless device configured withhigher layer parameter symPUSCH-UpPts for the serving cell c, K_(PUSCH)may be predefined (e.g., in LTE and/or NR specifications);for TDD UL/DL configuration 6 and a wireless device configured withhigher layer parameter symPUSCH-UpPts for the serving cell c, forexample, if the PUSCH transmission in subframe 2 or 7 is scheduled witha PDCCH/EPDCCH of DCI format 0/4 in which the LSB of the UL index is setto 1, K_(PUSCH)=6. For all other PUSCH transmissions, K_(PUSCH) may bepredefined (e.g., in LTE and/or NR specifications); for a serving cellwith frame structure type 3; for an uplink DCI format (e.g., DCI format0A/0B/4A/4B in LTE), with PUSCH trigger A set to 0, K_(PUSCH) may beequal to k+l, where k and 1 may be pre-defined in a specification (e.g.,in LTE and/or NR technologies specifications); for an uplink DCI format(e.g., DCI format 0A/0B/4A/4B in LTE), with PUSCH trigger A set to 1 andupon the detection of PDCCH with DCI CRC scrambled by CC-RNTI and with‘PUSCH trigger B’ field set to ‘1’, K_(PUSCH) may equal to p+k+l, wherep, k and l may be pre-defined in a specification (e.g., in LTE and/or NRtechnologies specifications). For example, if a wireless device detectedmultiple TPC commands in subframe (TTI, slot, and/or mini-slot)i−K_(PUSCH), the wireless device may use the TPC command in thePDCCH/EPDCCH with a DCI format (e.g., DCI format 0A/0B/4A/4B in LTE),which may schedule a PUSCH transmission in a subframe (TTI, slot, and/ormini-slot) i.

For a serving cell c and a wireless device (e.g., a non-BL/CE wirelessdevice), the wireless device may attempt to decode a PDCCH/EPDCCH of aDCI format (e.g., DCI format 0/0A/0B/4/4A/4B in LTE) with the wirelessdevice's C-RNTI or a DCI format (e.g., DCI format 0 in LTE and/or DCIformat 0_0/0_1 in NR), for SPS (or configured grant type1, and/orconfigured grant type 2) C-RNTI and a PDCCH of a DCI format (e.g., DCIformat 3/3A in LTE and/or DCI format 2_2 in NR) with this wirelessdevice's RNIT (e.g., TPC-PUSCH-RNTI) in every subframe (TTI, slot,and/or mini-slot) except if in DRX or if the serving cell c isdeactivated.

For a serving cell c and a wireless device (e.g., a BL/CE wirelessdevice configured with CEModeA), the wireless device may attempt todecode an MPDCCH of a DCI format (e.g., DCI format 6-0A in LTE) with thewireless device's C-RNTI or SPS (OR configured grant type1, and/orconfigured grant type 2) C-RNTI and an MPDCCH of a DCI format (e.g., DCIformat 3/3A in LTE and/or DCI format 2_2 in NR) with this wirelessdevice's RNTI (e.g., TPC-PUSCH-RNTI) in particular downlink subframes(e.g., every BL/CE downlink subframe (TTI, slot, and/or mini-slot))except if in DRX.

For a wireless device (e.g., a non-BL/CE wireless), the wireless devicemay use the δ_(PUSCH,c) provided in a DCI format (e.g., DCI format0/0A/0B/4/4A/4B in LTE and/or DCI format 0_0/0_1 in NR), for example, ifa DCI format (e.g., DCI format 0/0A/0B/4/4A/4B in LTE and/or DCI format0_0/0_1 in NR) for a serving cell c and a DCI format (e.g., DCI format3/3A in LTE and/or DCI format 2_2 in NR) are both detected in the samesubframe (TTI, slot, and/or mini-slot).

For a wireless device (e.g., a BL/CE wireless device configured withCEModeA), the wireless device may use the δ_(PUSCH,c) provided in thefirst DCI format (e.g., 6-0A), for example, if a first DCI format (e.g.,6-0A) for a serving cell c and a second DCI (e.g., DCI format 3/3A) areboth detected in the same subframe.

δ_(PUSCH,c) may be 0 dB for a subframe (TTI, slot, and/or mini-slot),for example, where no TPC command is decoded for a serving cell c or ifDRX occurs or i is not an uplink subframe (TTI, slot, and/or mini-slot)in TDD or FDD-TDD and the serving cell c frame structure type 2.

δ_(PUSCH,c) may be 0 dB, for example, if the subframe (TTI, slot, and/ormini-slot) i is not the first subframe (TTI, slot, and/or mini-slot)scheduled by a PDCCH/EPDCCH of DCI format 0B/4B.

The δ_(PUSCH,c) dB accumulated values signaled on a PDCCH/EPDCCH with aDCI format (e.g., DCI format 0/0A/0B/4/4A/4B in LTE and/or DCI format0_0/0_1 in NR) or an MPDCCH with a DCI format (e.g., DCI format 6-0A)may be given in a predefined table. δ_(PUSCH,c) may be 0 dB, forexample, if the PDCCH/EPDCCH with a DCI format (e.g., DCI format 0 inLTE) and/or the MPDCCH with a DCI format (e.g., DCI format 6-0A in LTE)are validated as an SPS (or configured grant Type 2) activation orrelease PDCCH/EPDCCH/MPDCCH.

The δ_(PUSCH,c) dB accumulated values signaled on PDCCH/MPDCCH with aDCI format (e.g., DCI format 3/3A) may be one of SET1 given in apredefined table (e.g., shown in FIG. 21) or SET2 given in a predefinedtable as determined by the parameter (e.g., TPC-Index) provided byhigher layers.

Positive TPC commands for a serving cell c may not be accumulated, forexample, if the wireless device has reached P_(CMAX,c)(i) for theserving cell c.

Negative TPC commands may not be accumulated, for example, if thewireless device has reached minimum power.

If the wireless device is not configured with a higher layer parameter(e.g., UplinkPowerControlDedicated) for a serving cell c, the wirelessdevice may reset accumulation for the serving cell c, for example, ifP_(O) _(_) _(UE) _(_) _(PUSCH,c) value is changed by higher layersand/or if the wireless device receives random access response messagefor the serving cell c.

If the wireless device is configured with a higher layer parameter(e.g., UplinkPowerControlDedicated) for a serving cell c, the wirelessmay reset accumulation corresponding to f_(c)(*) for the serving cell c,for example, if P_(O) _(_) _(UE) _(_) _(PUSCH,c) value has been changedby higher layers, or if the wireless device receives random accessresponse message for the serving cell c. If the wireless device isconfigured with a higher layer parameter (e.g.,UplinkPowerControlDedicated) for a serving cell c, the wireless devicemay reset accumulation corresponding to f_(c,2)(*) for the serving cellc, for example, if P_(O) _(_) _(UE) _(_) _(PUSCH,c,2) value has beenchanged by higher layers.

If the wireless device is configured with higher layer parameter (e.g.,UplinkPowerControlDedicated) for a serving cell c and/or if a subframe(TTI, slot, and/or mini-slot) i belongs to an uplink power controlsubframe (TTI, slot, and/or mini-slot) set 2 as indicated by the higherlayer parameter (e.g., tpc-SubframeSet), the wireless device may setf_(c)(i)=f_(c)(i−1). If the wireless device is configured with higherlayer parameter (e.g., UplinkPowerControlDedicated) for a serving cell cand/or if a subframe (TTI, slot, and/or mini-slot) i does not belong touplink power control subframe (TTI, slot, and/or mini-slot) set 2 asindicated by the higher layer parameter (e.g., tpc-SubframeSet), thewireless device may set f_(c,2)(i)=f_(c,2)(i−1).

The wireless device may set f_(c)(i)=δ_(PUSCH,c)(i−K_(PUSCH)) andf_(c,2)(i)=δ_(PUSCH,c)(i−K_(PUSCH)), for example, if accumulation is notenabled for a serving cell c based on the parameter (e.g.,Accumulation-enabled) provided by higher layers.δ_(PUSCH,c)(i−K_(PUSCH)) may be signaled on a PDCCH/EPDCCH with a DCI(e.g., DCI format 0/0A/0B/4/4A/4B) or an MPDCCH with a DCI (e.g., DCIformat 6-0A) for the serving cell c on a subframe (TTI, slot, and/ormini-slot) i−K_(PUSCH). For a wireless device (e.g., a BL/CE UEconfigured with CEModeA), the subframe (TTI, slot, and/or mini-slot)i−K_(PUSCH) may be the last subframe (TTI, slot, and/or mini-slot) inwhich the MPDCCH with DCI format 6-0A or MPDCCH with DCI format 3/3A maybe transmitted.

With respect to the value of K_(PUSCH), for FDD or FDD-TDD and servingcell frame structure type 1, the wireless device may set K_(PUSCH)=4.For TDD, if the wireless device is configured with more than one servingcell and the TDD UL/DL configuration of at least two configured servingcells are not the same, or if the wireless device is configured with aparticular parameter (e.g., EIMTA-MainConfigServCell) for at least oneserving cell, or FDD-TDD and serving cell frame structure type 2, the“TDD UL/DL configuration” may refer to the UL-reference UL/DLconfiguration for serving cell c. For one or more TDD UL/DLconfigurations (e.g., configurations 1-6), K_(PUSCH) may be predefined;

for TDD UL/DL configuration 0, if the PUSCH transmission in subframe(TTI, slot, and/or mini-slot) 2 or 7 is scheduled with a PDCCH/EPDCCH ofa DCI (e.g., DCI format 0/4) or an MPDCCH with a DCI (e.g., DCI format6-0A) in which the LSB of the UL index is set to 1, the wireless devicemay set K_(PUSCH)=7, and for all other PUSCH transmissions, K_(PUSCH)may be predefined.

For an unlicensed band, for example, a serving cell with frame structuretype 3 may be configured. For an uplink DCI format (e.g., 0A/4A) withPUSCH trigger A set to 0, K_(PUSCH) may be equal to k+l. k and l may bepre-defined in a specification (e.g., in LTE and/or NR technologiesspecifications). For an uplink DCI format (e.g., 0B/4B) with PUSCHtrigger A set to 0, K_(PUSCH) may be equal to k+l+i′ withi′==mod(n_(HARQ) _(_) _(ID) ^(i)−n_(HARQ) _(_) _(ID), N_(HARQ))niHARQ_ID may be HARQ process number in a subframe (TTI, slot, and/ormini-slot) i, and k, l, nHARQ_ID and NHARQ may be pre-defined in aspecification (e.g., in LTE and/or NR technologies specifications). Foran uplink DCI format (e.g., 0A/4A) with PUSCH trigger A set to 1 andupon the detection of PDCCH with DCI CRC scrambled by CC-RNTI and withPUSCH trigger B′ field set to ‘1’, K_(PUSCH) may be equal to p+k+l p, kand l may be pre-defined in a specification (e.g., in LTE, NR, and/orany other technologies specifications). For an uplink DCI format (e.g.,0B/4B) with PUSCH trigger A set to 1 and upon the detection of a PDCCHwith a DCI CRC scrambled by CC-RNTI and with PUSCH trigger B′ field setto ‘1’, K_(PUSCH) may be equal to p+k+l+i′ with i′=mod(n_(HARQ) _(_)_(ID) ^(i)−n_(HARQ) _(_) _(ID), N_(HARQ)) n_(HARQ) _(_) _(ID) ^(i) maybe an HARQ process number in a subframe (TTI, slot, and/or mini-slot) i,and p, k, l, n_(HARQ) _(_) _(ID) and N_(HARQ) may be pre-defined in aspecification (e.g., in LTE and/or NR technologies specifications).

-   -   A wireless device may use a TPC command in a PDCCH/EPDCCH with a        DCI (e.g., DCI format 0A/0B/4A/4B) which may schedule a PUSCH        transmission in a subframe (TTI, slot, and/or mini-slot) i., for        example, if the wireless device detected multiple TPC commands        in subframe (TTI, slot, and/or mini-slot) i−K_(PUSCH).

The δ_(PUSCH,c) dB absolute values signaled on a PDCCH/EPDCCH with a DCI(e.g., DCI format 0/0A/0B/4/4A/4B) or an MPDCCH with a DCI (e.g., DCIformat 6-0A) may be predefined. δ_(PUSCH,c) may be 0 dB, for example, ifthe PDCCH/EPDCCH with a DCI (e.g., DCI format 0, DCI format 0_0, DCIformat 0_1, DCI format 1_1, DCI format 1_0, DCI format 2_0, DCI format2_1, DCI format 2_2) or an MPDCCH with DCI format 6-0A may be validatedas an SPS (or configured grant type 1, and/or configured grant type 2)activation or release PDCCH/EPDCCH/MPDCCH.

For a wireless device (e.g., a non-BL/CE wireless device), the wirelessdevice may set f_(c)(i)=f_(c)(i−1) and f_(c,2)(i)=f_(c,2)(i−1) for asubframe (TTI, slot, and/or mini-slot) where, for example, noPDCCH/EPDCCH with a DCI format (e.g., DCI format 0/0A/0B/4/4A/4B) isdecoded for a serving cell c or where, for example, DRX occurs or i isnot an uplink subframe (TTI, slot, and/or mini-slot) in TDD or FDD-TDDand serving cell c frame structure type 2.

For a wireless device (e.g., a BL/CE wireless device configured withCEModeA), the wireless device may set f_(c)(i)=f_(c)(i−1) andf_(c,2)(i)=f_(c,2)(i−1) for a subframe (TTI, slot, and/or mini-slot)where, for example, no MPDCCH with DCI format 6-0A is decoded for aserving cell c or where, for example, DRX occurs or i is not an uplinksubframe (TTI, slot, and/or mini-slot) in TDD.

A wireless device may set f_(c)(i)=f_(c)(i−1), for example, if thewireless device is configured with higher layer parameter (e.g.,UplinkPowerControlDedicated) for a serving cell c and if a subframe(TTI, slot, and/or mini-slot) i belongs to an uplink power controlsubframe (TTI, slot, and/or mini-slot) set 2 as indicated by the higherlayer parameter (e.g., tpc-SubframeSet). The wireless device may setf_(c,2)(i)=f_(c,2)(i−1), for example, if the wireless device isconfigured with a higher layer parameter (e.g.,UplinkPowerControlDedicated) for a serving cell c and if a subframe(TTI, slot, and/or mini-slot) i does not belong to an uplink powercontrol subframe (TTI, slot, and/or mini-slot) set 2 as indicated by thehigher layer parameter tpc-SubframeSet.

For both types of f_(c)(*) (accumulation or current absolute), the firstvalue may be set as follows:

f_(c)(0) may be zero, for example, if P_(O) _(_) _(UE) _(_) _(PUSCH,c)value is changed by higher layers and a serving cell c is the primarycell, or if P_(O) _(_) _(UE) _(_) _(PUSCH,c) value is received by higherlayers and the serving cell c is a Secondary cell; Else,

-   -   The wireless device may set f_(c)(0)=ΔP_(rampup,c)+δ_(msg2,c),        for example, if the wireless device receives the random access        response message for a serving cell c δ_(msg2,c) may be the TPC        command indicated in the random access response corresponding to        the random access preamble transmitted in the serving cell c,        and

${\Delta \; P_{{rampup},c}} = {\min \left\lbrack {\left\{ {\max \left( {0,{P_{{CMAX},c} - \begin{pmatrix}{{10{\log_{10}\left( {M_{{PUSCH},c}(0)} \right)}} +} \\{{P_{{O\; \_ \; {PUSCH}},c}(2)} + \delta_{{msg}\; 2} +} \\{{{\alpha_{c}(2)} \cdot {PL}} + {\Delta_{{TF},c}(0)}}\end{pmatrix}}} \right)} \right\},{\Delta \; P_{{rampuprequested},c}}} \right\rbrack}$

-   -    and ΔP_(rampuprequested,c) may be provided by higher layers and        may correspond to the total power ramp-up requested by higher        layers from the first to the last preamble in the serving cell        c, M_(PUSCH,c)(0) may be the bandwidth of the PUSCH resource        assignment expressed in number of resource blocks valid for the        subframe (TTI, slot, and/or mini-slot) of first PUSCH        transmission in the serving cell c, and ΔTF,c(0) may be the        power adjustment of first PUSCH transmission in the serving cell        c.    -   The wireless device may set f_(c,2)(0)=0, for example, if P_(O)        _(_) _(UE) _(_) _(PUSCH,c,2) value is received by higher layers        for a serving cell c.

The setting of the wireless device transmit power P_(PUCCH) for thephysical uplink control channel (PUCCH) transmission in a subframe (TTI,slot, and/or mini-slot) i for a serving cell c may be defined by

${{P_{PUCCH}(i)} = {\min {\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{P_{0\_ \; {PUCCH}} + {PL}_{c} + {h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} +} \\{{\Delta_{F\; \_ \; {PUCCH}}(F)} + {\Delta_{TxD}\left( F^{\prime} \right)} + {g(i)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}},$

for example, if the serving cell c is the primary cell, for a firstPUCCH format (e.g., 1/1a/1b/2/2a/2b/3).

The setting of the wireless device transmit power P_(PUCCH) for thephysical uplink control channel (PUCCH) transmission in a subframe (TTI,slot, and/or mini-slot) i for a serving cell c may be defined by

${{P_{PUCCH}(i)} = {\min {\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{P_{0\_ \; {PUCCH}} + {PL}_{c} + {10{\log_{10}\left( {M_{{PUCCH},c}(i)} \right)}} +} \\{{\Delta_{{TF},c}(i)} + {\Delta_{F\; \_ \; {PUCCH}}(F)} + {g(i)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}},$

for example, if the serving cell c is the primary cell, for a secondPUCCH format (e.g., 4/5).

For the accumulation of TPC command for PUCCH, the wireless device mayassume that the wireless device transmit power P_(PUCCH) for PUCCH in asubframe (TTI, slot, and/or mini-slot) i may be computed byP_(PUCCH)(i)=min {P_(CMAX,c)(i), P₀ _(_) _(PUCCH)+PL_(c)+g(i)} [dBm],for example, if the wireless device is not transmitting PUCCH for theprimary cell.

P_(CMAX,c)(i) may be the configured wireless device transmit power insubframe (TTI, slot, and/or mini-slot) i for a serving cell c. For theaccumulation of TPC command for a PUCCH, the wireless device may computeP_(CMAX,c)(i) assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dB and ΔT_(C)=0 dB,for example, if the wireless device does not transmit a PUCCH and PUSCHin a subframe (TTI, slot, and/or mini-slot) i for the serving cell c.MPR, A-MPR, P-MPR and ΔT_(C) may be pre-defined in a specification(e.g., in a LTE, NR, and/or any other technologies specifications).

The parameter Δ_(F) _(_) _(PUCCH)(F) may be provided by higher layers. AΔ_(F) _(_) _(PUCCH)(F) value may correspond to a PUCCH format (F)relative to a PUCCH format (e.g., PUCCH format 1a) The PUCCH format (F)may be pre-defined in a specification (e.g., in LTE, NR, and/or anyother technologies specifications).

The value of Δ_(TxD)(F′) may be provided by higher layers, for example,if the wireless device may be configured by higher layers to transmit aPUCCH on two antenna ports. Each PUCCH format F′ may be pre-defined in aspecification (e.g., in LTE and/or NR technologies specifications);otherwise, the wireless device may set Δ_(TxD)(F′)=0.

h(n_(CQI), n_(HARQ), n_(SR)) may be a PUCCH format dependent valuen_(CQI) may correspond to the number of information bits for the channelquality information. The wireless device may set n_(SR)=1, for example,if a subframe (TTI, slot, and/or mini-slot) i is configured for SR forthe wireless device not having any associated transport block forUL-SCH, otherwise the wireless device may set n_(SR)=0. The value ofn_(HARQ) may be pre-defined in a specification (e.g., in LTE and/or NRtechnologies specifications), for example, if the wireless device isconfigured with more than one serving cell, or the wireless device isconfigured with one serving cell and transmitting using a PUCCH format(e.g., a PUCCH format 3). Otherwise, n_(HARQ) may be the number ofHARQ-ACK bits sent in the subframe (TTI, slot, and/or mini-slot) i.)

The wireless device may set h(n_(CQI), n_(HARQ), n_(SR))=0, for example,for a first PUCCH format (e.g., PUCCH format 1,1a and 1b).

For a second PUCCH format (e.g., PUCCH format 1b) with a channelselection, the wireless device may set

${{h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} = \frac{\left( {n_{HARQ} - 1} \right)}{2}},$

for example, if the wireless device is configured with more than oneserving cell. Otherwise, for example, h(n_(CQI),n_(HARQ), n_(SR))=0.

The wireless device may set

${h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} = \left\{ {\begin{matrix}{10{\log_{10}\left( \frac{n_{CQI}}{4} \right)}} & {{{if}\mspace{14mu} n_{CQI}} \geq 4} \\0 & {otherwise}\end{matrix},} \right.$

for example, for a third PUCCH format (e.g., PUCCH format 2, 2a, 2b) anda normal cyclic prefix.

The wireless device may set

${h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} = \left\{ {\begin{matrix}{10{\log_{10}\left( \frac{n_{CQI} + n_{HARQ}}{4} \right)}} & {{{{if}\mspace{14mu} n_{CQI}} + n_{HARQ}} \geq 4} \\0 & {otherwise}\end{matrix},} \right.$

for example, for a fourth PUCCH format (e.g., PUCCH format 2) and anextended cyclic prefix.

For a fifth PUCCH format (e.g., PUCCH format 3) and if a wireless devicetransmits HARQ-ACK/SR without periodic CSI, the wireless device may set

${{h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} = \frac{n_{HARQ} + n_{SR} - 1}{3}},$

for example, if the wireless device is configured by higher layers totransmit PUCCH format 3 on two antenna ports, or if the wireless devicetransmits more than a number of bits (e.g., 11 bits) of HARQ-ACK/SR.Otherwise, the wireless device may set

${h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} = {\frac{n_{HARQ} + n_{SR} - 1}{2}.}$

For a sixth PUCCH format (e.g., PUCCH format 3) and if a wireless devicetransmits HARQ-ACK/SR and periodic CSI, the wireless device may set

${{h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} = \frac{n_{HARQ} + n_{SR} + n_{CQI} - 1}{3}},$

for example, if the wireless device is configured by higher layers totransmit a PUCCH format (e.g., PUCCH format 3) on two antenna ports, orif the wireless device transmits more than a number of bits (e.g., 11bits) of HARQ-ACK/SR and CSI; Otherwise, for example, the wirelessdevice may set

${h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} = {\frac{n_{HARQ} + n_{SR} + n_{CQI} - 1}{2}.}$

For a seventh PUCCH format (e.g., PUCCH format 4), for example,M_(PUCCH,c)(i) may be the bandwidth of the PUCCH format 4 expressed innumber of resource blocks valid for a subframe (TTI, slot, and/ormini-slot) i and a serving cell c. For PUCCH format 5, for example, thewireless device may set M_(PUCCH,c)(i)=1.

The wireless device may set Δ_(TF,c)(i)=10 log₁₀(2^(1.25·BPRE(i))−1).The wireless device may set BPRE(i)=O_(UCI)(i)/N_(RE)(i). O_(UCI)(i) maybe the number of HARQ-ACK/SR/RI/CQI/PMI bits comprising CRC bitstransmitted on PUCCH format 4/5 in subframe (TTI, slot, and/ormini-slot) i. The wireless device may setN_(RE)(i)=M_(PUCCH,c)(i)·N_(sc) ^(RB)·N_(symb) ^(PUCCH) for PUCCH format4 and N_(RE)(i)=N_(sc) ^(RB)·N_(symb) ^(PUCCH)/2 for PUCCH format 5. Thewireless device may set N_(symb) ^(PUCCH)=2·(N_(symb) ^(UL)−1)−1, forexample, if shortened PUCCH format 4 and/or shortened PUCCH format 5 isused in subframe (TTI, slot, and/or mini-slot) i. Otherwise, forexample, N_(symb) ^(PUCCH)=2·(N_(symb) ^(UL)−1).

P_(O) _(_) _(PUCCH) may be a parameter computed as the sum of aparameter P_(O) _(_) _(NOMINAL) _(_) _(PUCCH) provided by higher layersand a parameter P_(O) _(_) _(UE) _(_) _(PUCCH) provided by higherlayers.

δ_(PUCCH) may be a device specific correction value (e.g., a UE-specificcorrection value), may be a TPC command, included in a PDCCH with a DCIformat (e.g., DCI format 1A/1B/1D/1/2A/2/2B/2C/2D) for the primary cell,or included in an MPDCCH (e.g., with DCI format 6-1A), or included in anEPDCCH (e.g., with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D) for the primarycell, or sent jointly coded with other device specific PUCCH correctionvalues on a PDCCH/MPDCCH (e.g., with DCI format 3/3A in LTE and/or DCIformat 2_2 in NR) of which CRC parity bits may be scrambled with a groupRNTI (e.g., TPC-PUCCH-RNTI).

For a wireless device (e.g., a non-BL/CE UE), for example, if thewireless device is not configured for EPDCCH monitoring, the wirelessdevice may attempt to decode a PDCCH of a DCI format (e.g., DCI format3/3A in LTE and/or DCI format 2_2 in NR) with the wireless device's RNTI(e.g., TPC-PUCCH-RNTI) and one or several PDCCHs of a DCI format (e.g.,1A/1B/1D/1/2A/2/2B/2C/2D) with the wireless device's C-RNTI or SPS (orconfigured grant type1, and/or configured grant type 2) C-RNTI on everysubframe (TTI, slot, and/or mini-slot), except if in DRX.

If, for example, a wireless device is configured for EPDCCH monitoring,the wireless device may attempt to decode, for example, a PDCCH of a DCIformat (e.g., DCI format 3/3A in LTE and/or DCI format2_2 in NR) withthe wireless device's RNTI (e.g., TPC-PUCCH-RNTI) and one or severalPDCCHs of DCI format 1A/1B/1D/1/2A/2/2B/2C/2D with the wireless device'sC-RNTI or SPS (or configured grant type1, and/or configured grant type2) C-RNTI, and one or several EPDCCHs of DCI format1A/1B/1D/1/2A/2/2B/2C/2D with the wireless device's C-RNTI or SPS (orconfigured grant type1, and/or configured grant type 2) C-RNTI.

For a wireless device (e.g., a BL/CE wireless device configured withCEModeA), the wireless device may attempt to decode an MPDCCH of a DCIformat (e.g., DCI format 3/3A in LTE and/or DCI format 2_2) with thewireless device's RNTI (e.g., TPC-PUCCH-RNTI) and an MPDCCH of DCIformat 6-1A with the wireless device's C-RNTI or SPS (or configuredgrant type1, and/or configured grant type 2) C-RNTI on a particularsubframe (e.g., every BL/CE downlink subframe, slot, and/or mini-slot),except if in DRX.

The wireless device may use the δ_(PUCCH) provided in aPDCCH/EPDCCH/MPDCCH, for example, if the wireless device decodes thePDCCH (e.g., with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D), the EPDCCH(e.g., with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D), or the MPDCCH (e.g.,with DCI format 6-1A), for the primary cell, and the correspondingdetected RNTI equals the C-RNTI or SPS (or configured grant type1,and/or configured grant type 2) C-RNTI of the wireless device, and theTPC field in the DCI format is not used to determine the PUCCH resource.The wireless device may use the δ_(PUCCH) provided in that PDCCH/MPDCCH,for example, if the wireless device decodes a PDCCH/MPDCCH with DCIformat 3/3A. Otherwise, for example, the wireless device may setδ_(PUCCH)=0 dB.

The wireless device may set

${g(i)} = {{g\left( {i - 1} \right)} + {\sum\limits_{m = 0}^{M - 1}{{\delta_{PUCCH}\left( {i - k_{m}} \right)} \cdot {g(i)}}}}$

may be the current PUCCH power control adjustment state and g(0) may bethe first value after reset. For FDD or FDD-TDD and primary cell framestructure type 1, the wireless device may set M=1 and k₀=4. For TDD,values of M and k_(m) may be pre-defined in a specification (e.g., inthe LTE and/or NR technologies specifications).

The δ_(PUCCH) dB values signaled on a PDCCH with a DCI format (e.g.,1A/1B/1D/1/2A/2/2B/2C/2D) or an EPDCCH with a DCI format (e.g.,1A/1B/1D/1/2A/2/2B/2C/2D) or an MPDCCH with a DCI format (e.g., 6-1A)may be given in a predefined table (e.g., as shown in FIG. 22).δ_(PUCCH) may be 0 dB, for example, if the PDCCH with a DCI format(e.g., 1/1A/2/2A/2B/2C/2D) or the EPDCCH with a DCI format (e.g.,1/1A/2A/2/2B/2C/2D) or the MPDCCH with a DCI format (e.g., 6-1A) may bevalidated as an SPS (or configured grant type1, and/or configured granttype 2) activation PDCCH/EPDCCH/MPDCCH, or the PDCCH/EPDCCH (e.g., withDCI format 1A) or MPDCCH (e.g., with DCI format 6-1A) may be validatedas an SPS (or configured grant type1, and/or configured grant type 2)release PDCCH/EPDCCH/MPDCCH.

The δ_(PUCCH) dB values signaled on a PDCCH/MPDCCH with a DCI format(e.g., DCI format 3/3A in LTE and/or DCI format 2_2 in NR) may be givenin a predefined table (e.g., as shown in FIG. 22 or Table 5.1.2.1-2 in3GPP TS 36.213 v.14.4.0: “Evolved Universal Terrestrial Radio Access(E-UTRA); Physical layer procedures”) as semi-statically configured byhigher layers.

The wireless device may set g(0)=0, for example, if P_(O) _(_) _(UE)_(_) _(PUCCH) value is changed by higher layers. Otherwise, for example,the wireless device may set g(0)=ΔP_(rampup)+δ_(msg2) δ_(msg2) may bethe TPC command indicated in the random access response corresponding tothe random access preamble transmitted in the primary cell, and

${{\Delta \; P_{rampup}} = {\min \left\lbrack {\left\{ {\max \left( {0,{P_{{CMAX},c} - \begin{pmatrix}{P_{0\_ \; {PUCCH}} +} \\{{PL}_{c} + {h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} +} \\{{\Delta_{F\; \_ \; {PUCCH}}(F)} + {\Delta_{TxD}\left( F^{\prime} \right)}}\end{pmatrix}}} \right)} \right\},{\Delta \; P_{rampuprequested}}} \right\rbrack}},$

for example, if the wireless device is transmitting a PUCCH in asubframe (TTI, slot, and/or mini-slot) i.

Otherwise, for example, the wireless device may set ΔP_(rampup)=min[{max(0, P_(CMAX,c)−(P₀ _(_) _(PUCCH)+PL_(c)))}, ΔP_(rampuprequested)].ΔP_(rampuprequested) may be provided by higher layers and may correspondto the total power ramp-up requested by higher layers from the first tothe last preamble in the primary cell.

-   -   Positive TPC commands for the primary cell may not be        accumulated, for example, if the wireless device has reached        P_(CMAX,c)(i) for the primary cell.

Negative TPC commands may not be accumulated, for example, if thewireless device has reached minimum power.

The wireless device may reset accumulation, for example, if P_(O) _(_)_(UE) _(_) _(PUCCH) value is changed by higher layers. The wirelessdevice may reset accumulation, for example, if the wireless devicereceives a random access response message for the primary cell. Thewireless device may reset accumulation g(i)=g(i−1), for example, if imay be not an uplink subframe (TTI, slot, and/or mini-slot) in TDD orFDD-TDD and primary cell frame structure type 2.

For a wireless device (e.g., a BL/CE wireless device configured withCEModeA), k=0, 1, . . . , N−1 may be determined byP_(PUCCH,c)(i_(k))=P_(PUCCH,c)(i₀), for example, if the PUCCH istransmitted in more than one subframe (TTI, slot, and/or mini-slot) i₀,i₁, . . . , i_(N-1), where i₀<i₁< . . . <i_(N-1), the PUCCH transmitpower in a subframe (TTI, slot, and/or mini-slot) i_(k).

For a wireless device (e.g., a BL/CE wireless device configured withCEModeB), the PUCCH transmit power in subframe (TTI, slot, and/ormini-slot) i_(k) may be determined by P_(PUCCH,c)(i_(k))=P_(CMAX,c)(i₀).

The setting of the wireless device transmit power P_(SRS) for the SRStransmitted on a subframe (TTI, slot, and/or mini-slot) i for a servingcell c may be defined by: for example, for serving cell c with framestructure type 2, and not configured for PUSCH/PUCCH transmission

P _(SRS,c)(i)=min {P _(CMAX,c)(i),10 log₁₀(M _(SRS,c))+P _(O) _(_)_(SRS,c)(m)+α_(SRS,c) ·PL _(c) +f _(SRS,c)(i)} [dBm];

Otherwise, for example, P_(SRS) may be defined by

P _(SRS,c)(i)=min {P _(CMAX,c)(i),P _(SRS) _(_) _(OFFSET,c)(m)+10log₁₀(M _(SRS,c))+P _(O) _(_) _(PUSCH,c)(j)+α_(c)(j)+PL _(c) +f _(c)(i)}[dBm].

P_(CMAX,c)(i) may be the configured wireless device transmit power in asubframe (TTI, slot, and/or mini-slot) i for a serving cell c. P_(SRS)_(_) _(OFFSET,c)(m) may be semi-statically configured by higher layersfor m=0 and m=1 for the serving cell c. For SRS transmission giventrigger type 0, the wireless device may set m=0. For SRS transmissiongiven trigger type 1, the wireless device may set m=1. M SRS,c may bethe bandwidth of the SRS transmission in the subframe (TTI, slot, and/ormini-slot) i for the serving cell c expressed in number of resourceblocks. f_(c)(i) may be the current PUSCH power control adjustment statefor the serving cell c. P_(O) _(_) _(PUSCH,c)(j) and α_(c)(j) may beparameters as pre-defined in a specification (e.g., in LTE, NR, and/orany other technologies specifications) for a subframe (TTI, slot, and/ormini-slot) i, where j=1. α_(SRS,c) may be the higher layer parameter(e.g., alpha-SRS) configured by higher layers for the serving cell c.P_(O) _(_) _(SRS,c)(m) may be a parameter comprising the sum of acomponent P_(O) _(_) _(NOMINAL) _(_) _(SRS,c)(m) provided from higherlayers for m=0 and 1 and a component P_(O) _(_) _(UE) _(_) _(SRS,c)(m)provided by higher layers for m=0 and 1 for the serving cell c. For SRStransmission given trigger type 0, the wireless device may set m=0. ForSRS transmission given trigger type 1, the wireless device may set m=1.

For serving cell c with frame structure type 2, and not configured for aPUSCH/PUCCH transmission, the current SRS power control adjustment statemay be given by F_(SRS,c)(i) and may be defined by: for example, thewireless device may set f_(SRS,c)(i)f_(SRS,c)(i−1)+δ_(SRS,c)(i−K_(SRS)), for example, if accumulation isenabled, and f_(SRS,c)(i)=δ_(SRS,c)(i−K_(SRS)), for example, ifaccumulation is not enabled based on a higher layer parameter (e.g.,Accumulation-enabled) for example, δ_(SRS,c)(i−K_(SRS)) may be acorrection value, and/or may be an SRS TPC command signaled on a PDCCH(e.g., with DCI format 3B in LTE and/or DCI format 2_3 in NR) in themost recent subframe (TTI, slot, and/or mini-slot) i−K_(SRS), whereK_(SRS)≥4. The wireless device may be not expected to receive differentSRS TPC command values for the serving cell c in the same subframe (TTI,slot, and/or mini-slot). For a serving cell c with frame structure type2, and not configured for PUSCH/PUCCH transmission, the wireless devicemay attempt to decode a PDCCH of a DCI format (e.g., DCI format 3B inLTE and/or DCI format 2_3 in NR) with CRC scrambled by a higher layerparameter (e.g., SRS-TPC-RNTI) in every subframe (TTI, slot, and/ormini-slot), except when in DRX or where the serving cell c isdeactivated. The wireless device may set δ_(SRS,c)=0 dB for a subframe(TTI, slot, and/or mini-slot), for example, where no TPC command in aPDCCH with a DCI format (e.g., DCI format 3B in LTE and/or DCI format2_3 in NR) is decoded for a serving cell c or where DRX occurs or i isnot an uplink/special subframe (TTI, slot, and/or mini-slot) in TDD orFDD-TDD and serving cell c frame structure type 2.

The δ_(SRS) dB values signaled on a PDCCH with a DCI format (e.g., DCIformat 3B in LTE and/or DCI format 2_3 in NR) may be predefined, forexample, if a higher layer parameter (e.g., fieldTypeFormat3B) indicatesa multi-bit (e.g., 2 bits) TPC command. The δ_(SRS) dB signaled on aPDCCH with a DCI format (e.g., DCI format 3B in LTE and/or DCI format2_3 in NR) may be predefined, for example, if a higher layer parameter(e.g., fieldTypeFormat3B) indicates 1-bit TPC command.

f_(SRS,c)(0) may be the first value after reset of accumulation, forexample, if accumulation is enabled. The wireless device may resetaccumulation, for a serving cell c, for example, if P_(O) _(_) _(UE)_(_) _(SRS,c) value is changed by higher layers. The wireless device mayreset accumulation for the serving cell c, for example, if the wirelessdevice receives random access response message for the serving cell c.

For both types of f_(SRS,c)(*) (accumulation or current absolute), thefirst value may be set as follows:

The wireless device may set f_(SRS,c)(0)=0, for example, if P_(O) _(_)_(UE) _(_) _(SRS,c) value is received by higher layers.

The wireless device may set f_(SRS,c)(0)=ΔP_(rampup,c)+δ_(msg2,c), forexample, if P_(O) _(_) _(UE) _(_) _(SRS,c) value is not received byhigher layers, and if the wireless device receives the random accessresponse message for a serving cell c. δ_(msg2,c) may be the TPC commandindicated in the random access response corresponding to the randomaccess preamble transmitted in the serving cell c and

${\Delta \; P_{{rampup},c}} = {\min \begin{bmatrix}{\left\{ {\max \begin{pmatrix}{0,} \\{P_{{CMAX},c} - \left( {{10{\log_{10}\left( {M_{{SRS},c}(0)} \right)}} +} \right.} \\\left. {{P_{{O\; \_ \; {SRS}},c}(m)} + {\alpha_{{SRS},c} \cdot {PL}_{c}}} \right)\end{pmatrix}} \right\},} \\{\Delta \; P_{{rampuprequested},c}}\end{bmatrix}}$

and ΔP_(rampuprequested,c) may be provided by higher layers and maycorrespond to the total power ramp-up requested by higher layers fromthe first to the last preamble in the serving cell c, M_(SRS,c)(0) maybe the bandwidth of the SRS transmission expressed in number of resourceblocks valid for the subframe of first SRS transmission in the servingcell c.

For a PUSCH, a wireless device may scale a linear value {circumflex over(P)}_(PUSCH,f,c)(i, j, q_(d), l) of the transmit power P_(PUSCH,f,c)(i,j, q_(d), l), with parameters in the following, for example, by theratio of the number of antenna ports with a non-zero PUSCH transmissionto the number of configured antenna ports for the transmission scheme.The resulting scaled power may be split across the antenna ports onwhich the non-zero PUSCH may be transmitted.

A wireless device may determine the PUSCH transmission powerP_(PUSCH,f,c)(i, j, q_(d), l) in PUSCH transmission period i as

${P_{{PUSCH},f,c}\left( {i,j,q_{d},l} \right)} = {\min \begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\; \_ \; {PUSCH}},f,c}(j)} + {10{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},f,c}^{PUSCH}(i)}} \right)}} +} \\{{{\alpha_{f,c}(j)} \cdot {{PL}_{f,c}\left( q_{d} \right)}} + {\Delta_{{TF},f,c}(i)} + {f_{f,c}\left( {i,l} \right)}}\end{Bmatrix}}$

[dBm], for example, if the wireless device transmits the PUSCH oncarrier f of serving cell c using parameter set configuration with indexj and PUSCH power control adjustment state with index l.

P_(CMAX,f,c)(i) may be the configured wireless device transmit power forcarrier f of serving cell c in a PUSCH transmission period i.

P_(O) _(_) _(PUSCH,f,c)(j) may be a parameter comprising the sum of acomponent P_(O) _(_) _(NOMINAL) _(_) _(PUSCH,f,c)(j) and a component,where P_(O) _(_) _(UE) _(_) _(PUSCH,f,c)(j), where j∈{0, 1, . . . ,J−1}. For a PUSCH (re)transmission corresponding to a random accessresponse grant, j=0, the wireless device may set and P_(O) _(_)_(NOMINAL) _(_) _(PUSCH,f,c)(0)=0, and P_(O) _(_) _(NOMINAL) _(_)_(PUSCH,f,c)(0)=P_(O) _(_) _(PRE)+Δ_(PREAMBLE) _(_) _(Msg3). Theparameter preambleInitialReceivedTargetPower (for P_(O) _(_) _(PRE)) andDelta-preamble-msg3 (for Δ_(PREAMBLE) _(_) _(Msg3)) may be provided byhigher layers for a carrier f of a serving cell c. For a PUSCH(re)transmission corresponding to a grant-free configuration orsemi-persistent grant, j=1, P_(O) _(_) _(NOMINAL) _(_) _(PUSCH,f,c)(1)may be provided by a higher layer parameter (e.g.,p0-nominal-pusch-withoutgrant), and P_(O) _(_) _(UE) _(_)_(PUSCH,f,c)(1) may be provided by a higher layer parameter p0-ue-puschfor a carrier f of the serving cell c. For jε{2, . . . , J−1}=S_(j), aP_(O) _(_) _(NOMINAL) _(PUSCH,f,c) (j) value, applicable for allj∈S_(j), may be provided by a higher layer parameter (e.g.,p0-nominal-pusch-withgrant) for each carrier f of the serving cell c,and a set of P_(O) _(_) _(UE) _(_) _(PUSCH,f,c)(j) values may beprovided by a set of one or more higher layer parameters (e.g.,p0-pusch-alpha-set) and a respective index by a higher layer parameter(e.g., p0alphasetindex) for a carrier f of the serving cell c. The sizeof the set may be J−2 and may be indicated by a higher layer parameter(e.g., num-p0-alpha-sets).

M_(RB,f,c) ^(PUSCH)(i) may be the bandwidth of the PUSCH resourceassignment expressed in number of resource blocks for a PUSCHtransmission period i on a carrier f of a serving cell c, and μ may bepredefined and/or semi-statically configured by one or more higher layerparameters.

For j=0, the wireless device may set α_(f,c)(j)−1. For j=1, α_(f,c)(1)may be provided by a higher layer parameter (e.g., alpha). For j∈S_(j),a set of α_(f,c)(j) values may be provided by a set of higher layerparameters (e.g., p0-pusch-alpha-set) and a respective index by higherlayer parameter p0alphasetindex for a carrier f of a serving cell c,where the size of the set may be J−2 and may be indicated by a higherlayer parameter (e.g., num-p0-alpha-sets).

PL_(f,c)(q_(d)) may be a downlink path-loss estimate (e.g., in dB)calculated by the wireless device using reference signal (RS) resourceq_(d) for a carrier f of a serving cell c. The wireless device may beconfigured with a number of RS resources by one or more higher layerparameters (e.g., num-pusch-pathlossReference-rs) and a respective setof RS configurations for the number of RS resources may be provided by ahigher layer parameter (e.g., pusch-pathloss-Reference-rs) that maycomprise one or both of a set of SS/PBCH block indexes provided by ahigher layer parameter (e.g., pusch-pathlossReference-SSB) and a set ofCSI-RS configuration indexes provided by a higher layer parameter (e.g.,pusch-pathlossReference-CSIRS). The wireless device may identify an RSresource in the set of RS resources that correspond to an SS/PBCH blockor to a CSI-RS configuration as provided by a higher layer parameter(e.g., pusch-pathlossreference-index). The wireless device may use theRS resources indicated by a value of an SRI field in one or more DCIformats (e.g., DCI format 0_0 or DCI format 0_1) that may schedule thePUSCH transmission to obtain the downlink path-loss estimate, forexample, if the wireless device is configured by a higher layerparameter (e.g., SRS-SpatialRelationInfo) a mapping between a set of SRSresources and a set of RS resources for obtaining a downlink path-lossestimate.

PL_(f,c)(q_(d)) may be PL_(f,c)(q_(d))=referenceSignalPower—higher layerfiltered RSRP. referenceSignalPower may be provided by higher layers andRSRP may be defined for the reference serving cell and the higher layerfilter configuration may be for the reference serving cell. For j=0,referenceSignalPower may be configured by a higher layer parameter(e.g., SS-PBCHBlockPower). For j>0, referenceSignalPower may beconfigured by a higher layer parameter (e.g., SS-PBCHBlockPower) or by,if periodic CSI-RS transmission is configured, a higher layer parameter(e.g., Pc-SS) providing an offset of the CSI-RS transmission powerrelative to the SS/PBCH block transmission power.

The wireless device may set as for Δ_(TF,f,c)(i) as Δ_(TF,f,c)(i)=10log₁₀((2^(BPRE·K) ^(s) −1)·β_(offset) ^(PUSCH)) for K_(s)=1.25 andΔ_(TF,f,c)(i)=0 for K_(s)=0. K_(s) may be provided by a higher layerparameter (e.g., deltaMCS-Enabled) provided for a carrier f and servingcell c. The wireless device may set Δ_(TF,f,c)(i)=0, for example, if thePUSCH transmission is performed over more than one layers.

BPRE and β_(offset) ^(PUSCH), for a carrier f and a serving cell c, maybe computed as below. The wireless device may set

${BPRE} = {\sum\limits_{r = 0}^{C - 1}{K_{r}/N_{RE}}}$

for PUSCH with UL-SCH data and BPRE=O_(CSI)/N_(RE) for CSI (e.g.,periodic/aperiodic CSI and/or SP CSI) transmission in a PUSCH withoutUL-SCH data. C may be the number of code blocks, K_(r) may be the sizefor code block r, O_(CSI) may be the number of CSI part 1 bitscomprising CRC bits, and N_(RE) may be the number of resource elementsdetermined as N_(RE)=M_(RB,f,c) ^(PUSCH)(i)·N_(symb,f,c) ^(PUSCH)(i)excluding REs used for DM-RS transmission. N_(symb,f,c) ^(PUSCH)(i) maybe a number of symbols for a PUSCH transmission period i on a carrier fof a serving cell c and C, K_(r) may be predefined and/orsemi-statically configured. The wireless device may set β_(offset)^(PUSCH)=1, for example, if the PUSCH comprises UL-SCH data. Thewireless device may set β_(offset) ^(PUSCH)=β_(offset) ^(CSI,1), forexample, if the PUSCH comprises CSI and does not include UL-SCH data.

For the PUSCH power control adjustment state for a carrier f of aserving cell c in a PUSCH transmission period i,δ_(PUSCH,f,c)(i−K_(PUSCH),l) may be a correction value, which may be aTPC command, and may be in a PDCCH with one or more DCI formats (e.g.,DCI format 0_0 or DCI format 0_1) that may schedule the PUSCHtransmission period i on the carrier f of the serving cell c or jointlycoded with other TPC commands in a PDCCH with one or more DCI formats(e.g., DCI format 2_2) having CRC parity bits scrambled by a particularRNTI (e.g., TPC-PUSCH-RNTI) that may be received by the wireless deviceprior to the PUSCH transmission.

For the PUSCH power control adjustment state for a carrier f of aserving cell c in a PUSCH transmission period i,f_(f,c)(i,l)=f_(f,c)(i−1,l)+δ_(PUSCH,f,c)(i−K_(PUSCH),l) may be thePUSCH power control adjustment state for the carrier f of the servingcell c and the PUSCH transmission period i, for example, if accumulationis enabled based on the parameter Accumulation-enabled provided byhigher layers. l∈{1, 2} for example, if the wireless device isconfigured with a higher layer parameter (e.g.,num-pusch-pcadjustment-states); otherwise, for example, l=1. For a PUSCH(re)transmission corresponding to a grant-free configuration orsemi-persistent grant, the value of l∈{1,2} may be provided to thewireless device by a higher layer parameter (e.g.,PUSCH-closed-loop-index). The wireless device may setδ_(PUSCH,f,c)(i−K_(PUSCH),l)=0 dB, for example, if the wireless devicemay not detect a TPC command for the carrier f of the serving cell c.The respective δ_(PUSCH,f,c) accumulated values may be predefined, forexample, if the PUSCH transmission is based on or in response to a PDCCHdecoding with a DCI format (e.g., DCI format 0_0 or DCI format 0_1, or2_2) having CRC parity bits scrambled by a particular RNTI (e.g.,TPC-PUSCH-RNTI).

FIG. 21 shows an example of δ_(PUSCH,f,c) accumulated values andabsolute values. A TPC Command Field (e.g., in DCI format 0_0, DCIformat 0_1, or DCI format 2_2, or DCI format 2_3 having CRC parity bitsscrambled by a particular RNTI (e.g., TPC-PUSCH-RNTI or TPC-SRS-RNTI))may be mapped to absolute δ_(PUSCH,c) value and/or accumulatedδ_(PUSCH,c) value. f_(f,c)(0,l) may be the first value after a reset ofaccumulation. Positive TPC commands for carrier f of serving cell c maynot be accumulated, for example, if the wireless device has reachedP_(CMAX,f,c)(i) for the carrier f of the serving cell c. Negative TPCcommands for the carrier f of the serving cell c may not be accumulated,for example, if the wireless device has reached minimum power forcarrier f of serving cell c. The wireless device may reset accumulationfor the carrier f of the serving cell c, for example, if P_(O) _(_)_(UE) _(_) _(PUSCH,f,c)(j) value is changed by higher layers, and/or ifα_(f,c)(j) value is changed by higher layers.

For the PUSCH power control adjustment state for a carrier f of aserving cell c in a PUSCH transmission period i,f_(f,c)(i,l)=δ_(PUSCH,f,c)(i−K_(PUSCH),l) may be the PUSCH power controladjustment state for the carrier f of the serving cell c and the PUSCHtransmission period i, for example, if the accumulation is not enabledbased on a particular parameter (e.g., Accumulation-enabled) provided byhigher layers. The respective δ_(PUSCH,c) absolute values may bepredefined (e.g., in FIG. 21), for example, if the PUSCH transmission isbased on or in response to a PDCCH decoding with a DCI format (e.g., DCIformat 0_0 or DCI format 0_1, or 2_2) having CRC parity bits scrambledby a particular RNTI (e.g., TPC-PUSCH-RNTI). The wireless device may setf_(f,c)(i,l)=f_(f,c)(i−1,l) for a PUSCH transmission period, forexample, if the wireless device does not detect a DCI format (e.g., DCIformat 0_0 or DCI format 0_1, or 2_2) having CRC parity bits scrambledby a particular RNTI (e.g., TPC-PUSCH-RNTI) for carrier f of servingcell c.

For the PUSCH power control adjustment state for a carrier f of aserving cell c in a PUSCH transmission period i, for both types off_(f,c)(*) (the accumulated or the current absolute values) the firstvalue may be set as follows: The wireless device may set f_(f,c)(0,l)=0,for example, if P_(O) _(_) _(UE) _(_) _(PUSCH,f,c)(j) value is changedby higher layers and serving cell c is the primary cell and/or if P_(O)_(_) _(UE) _(_) _(PUSCH,f,c)(j) value is received by higher layers andthe serving cell c is a secondary cell; Else, the wireless device mayset f_(f,c)(0,l)=ΔP_(rampup,f,c)+δ_(msg2,f,c), for example, if thewireless device receives the random access response message for thecarrier f of the serving cell c δ_(msg2,f,c) may be the TPC commandindicated in the random access response corresponding to the randomaccess preamble transmitted for the carrier f in the serving cell c, and

${\Delta \; P_{{rampup},f,c}} = {{\min \left\lbrack {\left\{ {\max \left( {0,{P_{{CMAX},f,c} - \begin{pmatrix}{{10{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},f,c}^{PUSCH}(0)}} \right)}} +} \\{{P_{{O\; \_ \; {PUSCH}},f,c}(0)} + {{\alpha_{f,c}(0)} \cdot {PL}_{c}} +} \\{{\Delta_{{TF},f,c}(0)} + \delta_{{{msg}\; 2},f,c}}\end{pmatrix}}} \right)} \right\},{\Delta \; P_{{rampuprequested},c}}} \right\rbrack}.}$

ΔP_(rampuprequested,f,c) may be provided by higher layers and maycorrespond to the total power ramp-up requested by higher layers fromthe first to the last random access preamble for carrier f in theserving cell c. M_(RB,f,c) ^(PUSCH)(0) may be the bandwidth of the PUSCHresource assignment expressed in number of resource blocks for the firstPUSCH transmission in carrier f of the serving cell c. Δ_(TF,f,c)(0) maybe the power adjustment of first PUSCH transmission in the carrier f ofthe serving cell c.

The wireless device may apply the procedures for MCG and SCG, forexample, if the wireless device is configured with an SCG. The term‘serving cell’ may refer to serving cell belonging to an MCG, forexample, if the procedures are used for the MCG. The term ‘serving cell’may refer to serving cell belonging to an SCG, for example, if theprocedures are used for the SCG. The term ‘primary cell’ may refer tothe PSCell of the SCG. The wireless device may use the procedures for aprimary PUCCH group and a secondary PUCCH group, for example, if thewireless device is configured with a PUCCH-SCell. The term ‘servingcell’ may refer to a serving cell belonging to the primary PUCCH group,for example, if the procedures are used for the primary PUCCH group. Theterm ‘serving cell’ may refer to a serving cell belonging to thesecondary PUCCH group, for example, if the procedures are used for thesecondary PUCCH group. The term ‘primary cell’ may refer to thePUCCH-SCell of the secondary PUCCH group.

A wireless device may determine a PUCCH transmission powerP_(PUCCH,f,c)(i, q_(u), q_(d), l) in a PUCCH transmission period as

${{P_{{PUCCH},f,c}\left( {i,q_{u},q_{d},l} \right)} = {\min {\begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\; \_ \; {PUCCH}},f,c}\left( q_{u} \right)} + {{PL}_{f,c}\left( q_{d} \right)} +} \\{{\Delta_{F\; \_ \; {PUCCH}}(F)} + {\Delta_{{TF},f,c}(i)} + {g_{f,c}\left( {i,l} \right)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}},$

for example, if the wireless device transmits the PUCCH on a carrier fin the primary cell c using PUCCH power control adjustment state withindex l.

P_(CMAX,f,c)(i) may be the configured wireless device transmit power fora carrier f of a serving cell c in a PUCCH transmission period i.

P_(O) _(_) _(PUCCH,f,c)(q_(u)) may be a parameter comprising the sum ofa component P_(O) _(_) _(NOMINAL) _(_) _(PUCCH), provided by a higherlayer parameter (e.g., P0-nominal-PUCCH) for a carrier f of a primarycell c, and a component P_(O) _(_) _(UE) _(_) _(PUCCH)(q_(u)) providedby a higher layer parameter (e.g., P0-PUCCH), where 0≤q_(u)<Q_(u). Q_(u)may be a size for a set of P_(O) _(_) _(UE) _(_) _(PUCCH) valuesprovided by a higher layer parameter (e.g., num-p0-pucch). The set ofP_(O) _(_) _(UE) _(_) _(PUCCH) values may be provided by a higher layerparameter (e.g., p0-pucch-set).

PL_(f,c)(q_(d)) may be a downlink path-loss estimate (e.g., in dB)calculated by the wireless device for a carrier f of the primary cell cusing RS resource q_(d), where 0≤q_(d)<Q_(d). Q_(d) may be a size for aset of RS resources provided by a higher layer parameter (e.g.,num-pucch-pathlossReference-rs). The set of RS resources may be providedby a higher layer parameter (e.g., pucch-pathlossReference-rs). The setof RS resources may comprise one or both of a set of SS/PBCH blockindexes provided by a higher layer parameter (e.g.,pucch-pathlossReference-SSB) and a set of CSI-RS configuration indexesprovided by a higher layer parameter (e.g.,pucch-pathlossReference-CSIRS). The wireless device may identify an RSresource in the set of RS resources that corresponds to an SS/PBCH blockor to a CSI-RS configuration as provided by a higher layer parameter(e.g., pucch-pathlossreference-index).

The parameter Δ_(F) _(_) _(PUCCH)(F) may be provided by a higher layerparameter (e.g., deltaF-pucch-f0) for a first PUCCH format (e.g., PUCCHformat 0), deltaF-pucch-f1 for a second PUCCH format (e.g., PUCCH format1), deltaF-pucch-f2 for a third PUCCH format (e.g., PUCCH format 2),deltaF-pucch-f3 for a fourth PUCCH format (e.g., PUCCH format 3), anddeltaF-pucch-f4 for a fifth PUCCH format (e.g., PUCCH format 4).Δ_(TF,f,c)(i) may be a PUCCH transmission power adjustment component fora carrier f of a primary cell c.

For the PUCCH power control adjustment state for a carrier f of aprimary cell c and a PUCCH transmission period i,δ_(PUCCH,f,c)(i−K_(PUCCH),l) may be a correction value, which may be aTPC command, and may be in a PDCCH with a DCI format (e.g., DCI format1_0 or DCI format 1_1) for the carrier f of the primary cell c that thewireless device may detect in PUCCH transmission period i−K_(PUCCH), orjointly coded with one or more TPC commands in a PDCCH with a DCI format(e.g., DCI format 2_2) having CRC parity bits scrambled by a particularRNTI (e.g., TPC-PUCCH-RNTI) and l∈{1, 2} as indicated by a higher layerparameter (e.g., num-pucch-pcadjustment-states). The δ_(PUCCH,f,c)(e.g., in dB) values signaled on a PDCCH with a DCI format (e.g., DCIformat 1_0 or DCI format 1_1 or DCI format 2_2) having CRC parity bitsscrambled by a particular RNTI (e.g., TPC-PUCCH-RNTI) may be predefined.

FIG. 22 shows an example of δ_(PUCCH,f,c) dB values. A TPC Command Fieldin a DCI format (e.g., DCI format 1_0 or DCI format 1_1 or DCI format2_2) having CRC parity bits scrambled by a particular RNTI (e.g.,TPC-PUCCH-RNTI) may be mapped to the accumulated δ_(PUCCH,c) values. Thewireless device may set δ_(PUCCH,f,c)(i−K_(PUCCH),l)=0 dB, for example,if the wireless device does not detect a TPC command for a carrier f ofthe primary cell c.

g_(f,c)(i,l)=g_(f,c)(i−1,l)+δ_(PUCCH,f,c)(i−K_(PUCCH),l) may be thecurrent PUCCH power control adjustment state and g_(f,c)(0,l)=0 may bethe first value after a reset, for example, for the PUCCH power controladjustment state for a carrier f of a primary cell c and a PUCCHtransmission period i. The wireless device may set g_(f,c)(0,l)=0, forexample, if P_(O) _(_) _(UE) _(_) _(PUCCH,f,c) value is changed byhigher layers; Else, for example, the wireless device may setg_(f,c)(0,l)=ΔP_(rampup,f,c)+δ_(msg2,f,c) δ_(msg2,f,c) may be the TPCcommand indicated in the random access response corresponding to therandom access preamble transmitted for the carrier f in the serving cellc. The wireless device may set ΔP_(rampup,f,c)=min [{max(0,P_(CMAX,f,c)−(P_(O) _(_) _(PUCCH,f,c)+PL_(c)+Δ_(F) _(_)_(PUCCH)(F)+Δ_(TF,f,c)+δ_(msg2,f,c)))}, ΔP_(rampuprequested,f,c)], forexample, if the wireless device transmits PUCCH; otherwise, for example,the wireless device may set ΔP_(rampup,f,c)=min [{max(0,P_(CMAX,f,c)−(P_(O) _(_) _(PUCCH,f,c)+PL_(c)))},ΔP_(rampuprequested,f,c)]. ΔP_(rampuprequested,f,c) may be provided byhigher layers and may correspond to the total power ramp-up requested byhigher layers from the first to the last preamble for the carrier f inprimary cell c, and Δ_(F) _(_) _(PUCCH)(F) may correspond to a firstPUCCH format (e.g., PUCCH format 0) or a second PUCCH format (e.g.,PUCCH format 1). The δ_(PUSCH,c) accumulated values may be predefined(e.g., in FIG. 21), for example, if the PUSCH transmission is based onor in response to a PDCCH detection with a DCI format (e.g., DCI format1_0 or DCI format 1_1). The wireless device may not accumulate positiveTPC commands for the carrier f in the primary cell c, for example, ifthe wireless device has reached P_(CMAX,c)(i) for the carrier f in theprimary cell c. The wireless device may not accumulate negative TPCcommands for the carrier f in the primary cell c, for example, if thewireless device has reached minimum power for the carrier f in theprimary cell c. The wireless device may reset accumulation for thecarrier f in the primary cell c, for example, if P_(O) _(_) _(UE) _(_)_(PUCCH,f,c) value is changed by higher layers.

For a transmit power control of an SRS, the linear value {circumflexover (P)}_(SRS,f,c)(i, q_(s), l) of the transmit power P_(SRS,f,c)(i,q_(s), l) may be split equally across the configured antenna ports forSRS. A wireless device may determine the SRS transmission powerP_(SRS,f,c)(i, q_(s), l) in SRS transmission period i as

${{P_{{SRS},f,c}\left( {i,q_{s},l} \right)} = {\min {\begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\; \_ \; {SRS}},f,c}\left( q_{s} \right)} + {10{\log_{10}\left( {2^{\mu} \cdot {M_{{SRS},f,c}(i)}} \right)}} +} \\{{{\alpha_{{SRS},f,c}\left( q_{s} \right)} \cdot {{PL}_{f,c}\left( q_{s} \right)}} + {h_{f,c}\left( {i,l} \right)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}},$

for example, if the wireless device transmits the SRS on a carrier f ofa serving cell c using SRS power control adjustment state with index l.

P_(CMAX,f,c)(i) may be the configured wireless device transmit power fora carrier f of a serving cell c in an SRS transmission period i. P_(O)_(_) _(SRS,f,c)(q_(s)) may be provided by a higher layer parameter(e.g., p0-srs) for an SRS resource set q_(s). M_(SRS,f,c)(i) may be theSRS bandwidth expressed in number of resource blocks for the SRStransmission period i on the carrier f of the serving cell c and μ maybe predefined and/or semi-statically configured. α_(SRS,f,c)(q_(s)) maybe provided by a higher layer parameter (e.g., alpha-srs) for the SRSresource set q_(s).

PL_(f,c)(q_(s)) may be a downlink path-loss estimate (e.g., in dB)calculated by the wireless device for a carrier f of a serving cell cand an SRS resource set q_(s) using an RS resource provided by a higherlayer parameter (e.g., srs-pathlossReference-rs). The RS resource may beselected from a set of RS resources that may comprise a set of SS/PBCHblock indexes provided by a higher layer parameter (e.g.,srs-pathlossReference-SSB) and a set of CSI-RS configuration indexesprovided by a higher layer parameter (e.g.,srs-pathlossReference-CSIRS).

For the SRS power control adjustment state for a carrier f of a servingcell c and an SRS transmission period i, the wireless device may seth_(f,c)(i,l)=f_(f,c)(i,l), for example, if a higher layer parameter(e.g., srs-pcadjustment-state-config) indicate a same power controladjustment state for SRS transmissions and PUSCH transmissions.

For the SRS power control adjustment state for a carrier f of a servingcell c and an SRS transmission period i, the wireless device may seth_(f,c)(i)=h_(f,c)(i−1)+δ_(SRS,f,c)(i−K_(SRS)), for example, if a higherlayer parameter (e.g., srs-pcadjustment-state-config) indicates aseparate power control adjustment state between SRS transmissions andPUSCH transmissions and/or if the accumulation is enabled based on aparticular parameter (e.g., Accumulation-enabled-srs) provided by higherlayers. δ_(SRS,f,c)(i−K_(SRS)) may be jointly coded with other TPCcommands in a PDCCH with a DCI format (e.g., DCI format 2_3) having CRCparity bits scrambled by a particular RNTI (e.g., TPC-SRS-RNTI) that maybe received by the wireless device prior to the SRS transmission andaccumulative values of S_(SRS,f,c)(i−K_(SRS)) may be predefined (e.g.,in FIG. 21). The wireless device may set S_(SRS,f,c)(i−K_(SRS))=0 (e.g.,in dB), for example, if the wireless device does not detect a TPCcommand for serving cell c. h_(f,c)(0) may be the first value after areset of the accumulation. Positive TPC commands for the serving cell cmay not be accumulated, for example, if the wireless device has reachedP_(CMAX,f,c)(i) for the carrier f of the serving cell c. Negative TPCcommands may not be accumulated, for example, if the wireless device hasreached minimum power for the carrier f of the serving cell c. Awireless device may reset accumulation for the carrier f of the servingcell c, for example, if P_(O) _(_) _(SRS,f,c) value is changed by higherlayers and/or if α_(SRS,f,c) value is changed by higher layers.

For the SRS power control adjustment state for a carrier f of a servingcell c and an SRS transmission period i, the wireless device may seth_(f,c)(i)=δ_(SRS,f,c)(i−K_(SRS)), for example, if a higher layerparameter (e.g., srs-pcadjustment-state-config,) indicates a separatepower control adjustment state between SRS transmissions and PUSCHtransmissions and/or if the accumulation is not enabled based on aparameter (e.g., Accumulation-enabled-srs) provided by higher layers,jointly coded with other TPC commands in a PDCCH with a DCI format(e.g., DCI format 2_3) having CRC parity bits scrambled by a particularRNTI (e.g., TPC-SRS-RNTI) that may be received by the wireless deviceprior to the SRS transmission and absolute values ofS_(SRS,f,c)(i−K_(SRS)) may be predefined (e.g., in FIG. 21). Theδ_(PUSCH,c) absolute values may be predefined (e.g., in FIG. 21), forexample, if a DCI format (e.g., DCI format 2_3) has CRC scrambled by aparticular RNTI (e.g., TPC-SRS-RNTI). The wireless device may seth_(f,c)(i)=h_(f,c)(i−1) for an SRS transmission period i, for example,if the wireless device does not detect a DCI (e.g., DCI format 2_3)having CRC scrambled by a particular RNTI (e.g., TPC-SRS-RNTI) forcarrier f of serving cell c.

A base station (e.g., a gNB) may send, to a wireless device (e.g., aUE), a DCI indicating that the wireless device activates SP CSIreporting or a DCI indicating that the wireless device deactivates SPCSI reporting. At least one set of one or more SP CSI report settingsfor PUSCH or PUCCH may be RRC configured. For example, the base stationmay send an RRC message that comprises configuration information of theSP CSI report settings for PUSCH and/or configuration information of theSP CSI report settings for PUCCH. A DCI scrambled with a particular RNTI(e.g., SP CSI C-RNTI) and/or transmitted via one or more controlchannels (e.g., PDCCH) may indicate an activation or deactivation(suspending or releasing) of at least one of the one or more SP CSIreports. For example, a wireless device may receive a PDCCH from a basestation and extract, from the received PDCCH, one or more DCIs. Thewireless device may determine whether at least one of the one or moreDCIs is scrambled with SP CSI C-RNTI. The wireless device may check oneor more values of one or more fields of the at least one DCI scrambledwith the SP CSI C-RNTI to determine the activation or deactivation(suspending or releasing).

FIG. 23 shows an example of using a DCI for activating and deactivating(suspending or releasing) SP CSI reporting. A base station 2310 (e.g., agNB) may semi-statically configure at least one SP CSI report setting.The DCI 2351 activating or the DCI 2352 deactivating the SP CSIreporting (e.g., SP CSI reports 2361, 2362, 2363) may comprise at leastone field indicating the SP CSI reporting.

At least one first DCI (e.g., DCIs 2351, 2352) explicitly indicating anactivation or deactivation (suspension or releasing) of SP CSI may beconfigured (e.g., in an NR system). For example, the base station 2310may transmit the at least one first DCI via a PDCCH addressed by a firstRNTI (e.g., SP CSI RNTI). The at least one first DCI may comprise atleast one of the following fields: at least one first field indicatingat least one CSI request field; at least one second field indicating atleast one SP CSI report that may be RRC configured; and/or at least onethird field indicating an activation or deactivation (e.g., suspendingor releasing) of the at least one SP CSI report, for example, a firstvalue of the at least one third field may indicate the activation, and asecond value of the at least one third field may indicate thedeactivation. Based on or in response to receiving the at least onefirst DCI, a wireless device 2320 (e.g., a UE) may activate ordeactivate the at least one SP CSI report.

A wireless device (or a base station) may transmit data (e.g., CSIreport) via a recurred resource for a long time, for example, if the SPCSI is erroneously activated (deactivated, suspended, or released). Thedata transmission via a recurred resource for a long time may cause orgenerate an undesirable interference. A process for validating theactivation and/or deactivation of SP CSI (e.g., SP CSI reporting) forthe wireless device 2320 and/or the base station 2310 may be configured(e.g., in an NR system). For example, the wireless device 2320 mayvalidate an SP CSI assignment downlink control channel (e.g., PDCCH,ePDCCH, mPDCCH, etc), on a DCI, for example, if at least one of thefollowing conditions are met: the CRC parity bits obtained for the PDCCHpayload are scrambled with a particular RNTI (e.g., SP CSI RNTI)assigned for SP CSI; and/or one or more fields (e.g., a new dataindicator (NDI) field) for a DCI format are set to predefined value(e.g., NDI=‘0’).

The wireless device 2320 may receive the DCI 2351 (or DCI 2352) from thebase station 2310. The wireless device 2320 may achieve a validation ofactivation and/or deactivation of SP-CSI by determining that CRC paritybits of the DCI 2351 (or DCI 2352) are scrambled with a particular RNTI(e.g., SP-CSI RNTI) and by checking if one or more fields for the DCIformat of the received DCI are set to the one or more predefined values.The one or more fields may be at least one of the following: a TPCcommand for PUSCH or PUCCH, a cyclic shift demodulation reference signal(DM RS), a modulation and coding scheme and redundancy version, an HARQprocess number, a modulation and coding scheme, a redundancy version, aresource block assignment, a repetition number, or any combinationthereof, etc. The one or more predefined values may be one or morevalues of one or more DCI fields defined (e.g., in NR specifications).

FIG. 24A and FIG. 24B show examples of the one or more fields set to theone or more predefined values for the validation of the activationand/or deactivation (suspending, or releasing) of SP CSI. A first field(e.g., a TPC command for scheduled PUSCH field in FIG. 24A) may be usedfor the validation of the activation and deactivation (suspending, orreleasing). One or more fields of DCI formats shown in FIG. 24A may beexample fields for a validation of activation. One or more fields of DCIformats shown in FIG. 24B may be example fields for a validation ofdeactivation, suspending, or releasing. One or more fields of DCIformats shown in FIG. 24B may be example fields for a validation ofactivation while one or more fields of DCI formats shown in FIG. 24A maybe example fields for a validation of deactivation, suspending, orreleasing. One or more fields of the same DCI format may indicate boththe validation of activation and the validation of deactivation(suspending or releasing). For example, a first value of the one or morefields of the same DCI format may indicate the validation of activation,and a second value of the one or more fields of the same DCI format mayindicate the validation of deactivation.

FIG. 25A and FIG. 25B show examples of the one or more fields set to theone or more predefined values for the validation of the activationand/or deactivation (suspending, or releasing) of SP CSI. At least onefirst field used for the validation of activation (e.g., the repetitionnumber in FIG. 25B) may not be used for the validation of deactivation.For example, FIG. 25A may be example fields for a validation ofdeactivation, suspending, or releasing, and FIG. 25B may be examplefields for a validation of activation. As shown in FIG. 25B, forexample, the “repetition number” field of the 8^(th) DCI format and/or9^(th) DCI format may be used as a field for a validation of activationof SP CSI but may not be used as a field for a validation ofdeactivation of SP CSI.

At least one first field used for the validation of deactivation(suspending or releasing) may not be used for the validation ofactivation. For example, FIG. 25B may be example fields for a validationof deactivation, suspending, or releasing, and FIG. 25A may be examplefields for a validation of activation. The “repetition number” field ofthe 8^(th) DCI format and/or 9^(th) DCI format may be used as a fieldfor a validation of deactivation (suspending or releasing) of SP CSI butmay not be used as a field for a validation of activation of SP CSI.

The wireless device may determine the received DCI information as avalid SP CSI activation or deactivation (suspending, or releasing), forexample, if a validation is successfully performed. The wireless devicemay activate or deactivate (release, or suspend) SP CSI, for example,based on one or more predefined values of the one or more fields of thereceived DCI. The wireless device may assume and/or categorize thereceived DCI as a DCI received with a non-matching CRC, for example, ifthe validation is not successful.

A wireless device may transmit at least one SP CSI report via a PUSCH orPUCCH, for example, based on or in response to receiving a DCIactivating SP CSI. The transmission of the at least one SP CSI reportmay be based on the SP CSI report setting associated with the at leastone SP CSI report. Although the SP CSI report may be transmitted via adata channel (e.g., PUSCH), the transmission of the SP CSI report on thedata channel may be different from a transmission of general data (e.g.,UL-SCH data) on the data channel. A transmission of control data (e.g.,SP CSI report) may be different from a transmission of UL-SCH data, forexample, in terms of at least one of the following: the number of bitsto be transmitted, the bandwidth of the resource assignment, or one ormore open loop power control parameters (e.g., P_(O) _(_)_(PUSCH,f,c)(j), P_(O) _(_) _(PUSCH,c)(j), P_(O) _(_)_(PUCCH,f,c)(q_(u)), P_(O) _(_) _(PUCCH), α_(c)(j), or α_(f,c)(j)). Thewireless device may adjust or change one or more power controlparameters for a transmission of the SP CSI report via a PUSCH or PUCCH.For example, at least one of the one or more power control parametersmay not be configured for a data (e.g., UL-SCH and/or multiplexed dataof UL-SCH data and control data) transmission but may be configured foran SP CSI transmission.

A correction value (e.g., a TPC command, δ_(PUSCH,f,c)(i−K_(PUSCH), l)or δ_(PUSCH,c)(i−K_(PUSCH)), etc.) may be an adjustment of uplinktransmit power value subject to a previous transmission. A base stationmay transmit a request that may cause the wireless device to increase ordecrease an uplink transmit power for an upcoming transmission. Forexample, the base station may transmit the request by adding thecorrection value in a DCI and by transmitting the DCI comprising thecorrection value. The correction value may indicate an incremental powerfrom the current power value. A wireless device may be configured toselect, for a transmission of the SP CSI report, one or more values ofthe one or more power control parameters. The selection of the one ormore values for the SP CSI report may change the uplink channelcondition. For example, the change of P_(O) _(_) _(PUSCH,f,c)(j) orα_(f,c)(j) may result in the change of transmit power (e.g., to behigher or lower than the transmit power of the previous transmission).

The wireless device may set the correction value to accommodate thechange of uplink channel condition, for example, based on or in responseto receiving a DCI indicating an activation or deactivation of SP CSI.For example, the wireless device may set the correction value to a valuethat may be independently determined regardless of one or more values ofthe previous transmission.

The wireless device may receive an indication of an SP CSI activationvia a first DCI and may receive an indication of an SP CSI deactivationvia a second DCI. The first DCI (or second DCI) may comprise a fieldindicating a TPC command and other fields indicating HARQ processnumber, redundancy version, modulation and coding scheme, resource blockassignment, etc. For the activation (or deactivation) of SP CSI, the oneor more fields (e.g., for the TPC command, the HARQ process number, theredundancy version, etc., and/or any combinations thereof) in the firstDCI (or the second DCI) may be used for a validation of SP CSIactivation (or deactivation). For example, the TPC command, the HARQprocess number, the redundancy version, etc. shown in FIG. 24A and FIG.24B may be used for the validation. The wireless device may set thecorrection value to a first value, for example, based on or in responseto receiving the first DCI indicating an activation of SP CSI. The firstvalue may be independently determined regardless of the value indicatedby the TPC command in the first DCI. For example, the first value may bepredefined or semi-statically configured. The first value may be, forexample, zero or any other value. The wireless device may set thecorrection value to a second value, for example, based on the receivedsecond DCI indicating a deactivation of SP CSI (e.g., SP CSI reporting).The second value may be independently determined regardless of the valueindicated by the TPC command in the second DCI. For example, the secondvalue may be predefined or semi-statically configured. The second valuemay be, for example, zero or any other value. The second value may beequal to, or different from, the first value.

FIG. 26 shows an example of adjusting (e.g., changing, setting,initializing, etc.) a correction value after receiving a DCI associatedwith SP CSI. For example, a wireless device 2620 (e.g., a UE) may set acorrection value to a first value for an initial SP CSI report 2661, forexample, after or in response to receiving a first DCI 2651 indicatingan activation of SP CSI. The first DCI 2651 may indicate at least onesetting for SP CSI report(s) (e.g., SP CSI reports 2661, 2662, 2663,etc.). The wireless device 2620 may set the correction value to a secondvalue for a data transmission 2671 other than the SP CSI report, forexample, after or in response to receiving a second DCI 2652 indicatinga deactivation of SP CSI (e.g., SP CSI reporting). The first and secondvalues may be set to such values that may prevent the wireless device2620 from underestimate or overestimate the required uplink transmitpower, for example, if the uplink channel condition is changed (e.g.,after receiving the first DCI 2651 or the second DCI 2652).

The wireless device 2620 may receive, from a base station 2610 (e.g., agNB), at least one message comprising at least one of: one or more powercontrol parameters for a transmission of at least one SP CSI report; atleast one second parameter indicating at least one SP CSI resourcesetting of the at least one SP CSI report; at least one third parameterindicating at least one SP CSI report setting of the at least one SP CSIreport; and/or at least one fourth parameter indicating at least one SPCSI measurement setting of the at least one SP CSI report. The wirelessdevice 2620 may receive the first DCI 2651 indicating an activation ofat least one SP CSI report (e.g., activation of SP CSI reporting). Thewireless device 2620 may determine a first transmission power for astarting (or initial) transmission (e.g., the transmission of the SP CSIreport 2661) of the at least one SP CSI report, for example, after or inresponse to the first DCI 2651 indicating the activation, at least basedon: the one or more power control parameters and/or at least onecorrection value being set to a predefined value (e.g., zero). Thewireless device 2620 may transmit the at least one SP CSI report via aPUSCH using the first transmission power.

The first DCI 2651 may comprise a first TPC command indicating a firstvalue. The first value of the first TPC command may be independentlydetermined regardless of the at least one correction value. The PUSCHmay be indicated by the at least one SP CSI resource setting, the atleast one SP CSI report setting, and/or the at least one SP CSImeasurement setting. The wireless device 2620 may receive the second DCI2652 indicating a deactivation of at least one SP CSI report (e.g.,deactivation of SP CSI reporting). The wireless device 2620 maydetermine the at least one correction value being set to a predefinedvalue (e.g., zero) for the data 2671 (e.g., UL-SCH data) on PUSCH, forexample, after or in response to receiving the second DCI 2652.

One or more MAC CEs may indicate an activation or deactivation of SPCSI. At least one set of one or more SP CSI report settings for PUCCH(or PUSCH) may be RRC configured. For example, at least one of the oneor more SP CSI report settings for PUCCH (or PUSCH) may be configured inRRC with one or more PUCCH resources (or PUSCH resources) that may beused for transmitting one or more SP CSI reports. A transmission of theone or more SP CSI reports via the one or more PUCCH resources (or PUSCHresources) may be activated by a MAC CE.

The MAC CE may comprise at least one logical channel ID (LCID)indicating whether the MAC CE is for an activation and/or deactivationof SP CSI. For example, the MAC CE may comprise an LCID assigned toindicate an activation and deactivation with at least one fieldindicating whether the MAC CE is for an activation or deactivation. Forexample, two LCIDs (e.g., first and second LCIDs) may be respectivelyassigned to an activation (e.g., indicated by the first LCID) anddeactivation (e.g., indicated by the second LCID). The MAC CE maycomprise one or more fields indicating at least one of the following: atleast one SP CSI report setting, at least one SP CSI resource setting,or at least one SP CSI measurement setting. The MAC CE may be used toactivate or deactivate (release or suspend) the one or more PUCCHresources (or PUSCH resources) scheduled (configured, or granted) for atransmission of the at least one SP CSI report.

A wireless device may, based on at least one SP CSI setting, startmeasuring SP CSI and transmitting the SP CSI report, for example, afteror in response to receiving a first MAC CE indicating an activation ofat least one SP CSI report. The at least one SP CSI setting may beassociated with the at least one SP CSI report and may comprise at leastone of the following: at least one SP CSI report setting, at least oneSP CSI resource setting, and/or at least one SP CSI measurement setting.The wireless device may receive a second MAC CE indicating adeactivation of at least one SP CSI report (e.g., deactivation of SP CSIreporting). The wireless device may deactivate a transmission of the atleast one SP CSI report, for example, after or in response to receivingthe second MAC CE. The wireless device may release (or suspend) one ormore downlink assignments of SP CSI and/or one or more PUCCH resources(or PUSCH resources) scheduled (configured, or granted) for thetransmission of the at least one SP CSI report, for example, after or inresponse to receiving the second MAC CE.

The at least one SP CSI setting may be indicated by the first and/or thesecond MAC CE. For example, the first and/or second MAC CE may compriseat least one selection command indicating at least one CSI reportingsetting indication. The first and/or the second MAC CE may comprise oneor more indices indicating the at least one SP CSI setting. The one ormore indices may comprise at least one of the following: a first indexindicating one of at least one SP CSI report setting, a second indexindicating one of at least one SP CSI resource setting, or a third indexindicating one of at least one SP CSI measurement setting. The at leastone SP CSI setting may be semi-statically configured by RRC.

FIG. 27 shows an example of adjusting a correction value after or inresponse to receiving a first MAC CE 2751 activating SP CSI and/orreceiving a second MAC CE 2752 deactivating the SP CSI. A base station2710 (e.g., a gNB) may transmit, to a wireless device 2720 (e.g., a UE),the first MAC CE 2751 activating SP CSI. The base station 2710 maytransmit one or more SP CSI-RS (not shown) to the wireless device 2720,for example, after transmitting the first MAC CE 2751. The wirelessdevice 2720 may, based on one or more resource configuration parametersassociated with the at least one SP CSI setting, start measuring SP CSIassociated with the at least one SP CSI setting and may transmit atleast one report 2761, 2762, 2763 of the measured SP CSI, for example,after or in response to receiving the first MAC CE 2751 indicating anactivation of at least one SP CSI setting. The measurement of the SP CSImay comprise receiving one or more SP CSI-RS and measuring, based on theone or more SP CSI-RS, the SP CSI. The wireless device 2720 may need todetermine a correction value (and/or a TPC command) of an uplinktransmit power of the at least one SP CSI report 2761, 2762, 2763 to betransmitted via PUCCH (or PUSCH). The correction value may betransmitted via a DCI (e.g., L1 physical layer) scrambled by aparticular RNTI (e.g., SP CSI RNTI) assigned for SP CSI. There may be noTPC command that the wireless device 2720 may use to determine an uplinktransmit power for a transmission of the at least one SP CSI report2761, 2762, 2763 (e.g., an initial transmission 2761 of the at least oneSP CSI report after activating the SP CSI), for example, if the wirelessdevice 2720 activates the at least one SP CSI setting. The wirelessdevice 2720 may set the correction value to a first value (e.g., zero)for the transmission of the at least one SP CSI report 2761, 2762, 2763,for example, after or in response to determining that no TPC command hasbeen detected for the transmission. There may be a TPC command that thewireless device 2720 may use to determine an uplink transmit power for atransmission of the at least one SP CSI report 2761, 2762, 2763 (e.g.,an initial transmission 2761 of the at least one SP CSI report afteractivating the SP CSI), for example, if the wireless device 2720activates the at least one SP CSI setting. For example, the wirelessdevice 2720 may receive, at slot (mini-slot, subframe, or TTI)i-K_(PUCCH), a first DCI (e.g., a DCI comprising an uplink grant and/ora DCI comprising a group TPC command(s), e.g., DCI format 2_2)comprising a field indicating a first TPC command for a transmission atslot (mini-slot, subframe, or TTI) i. The i-K_(PUCCH) may besemi-statically configured by an RRC message, dynamically indicated by aDCI, and/or predefined. The transmission at slot (e.g., mini-slot,subframe, or TTI) i may be scheduled (granted, or configured) for the atleast one SP CSI setting. The physical layer may not have informationabout when the transmission of the at least one SP CSI report over PUCCH(or PUSCH) will be activated by the MAC layer, for example, if thetransmission is activated by a MAC CE. The first TPC command transmittedvia the first DCI may not be for the transmission of the at least one SPCSI report 2761, 2762, 2763. The wireless device 2720 may ignore thefirst TPC command received via the first DCI for the transmissions ofthe at least one SP CSI report 2761, 2762, 2763 (e.g., an initialtransmission 2761 of the at least one SP CSI report), for example, afteror in response to receiving the MAC CE 2751 indicating an activation ofa transmission of the at least one SP CSI report 2761, 2762, 2763 (e.g.,activation of SP CSI reporting). The wireless device 2720 may set thecorrection value to a first value (e.g., zero) that may be predefinedand/or semi-statically configured. The wireless device 2720 may set,based on an indication of activating the at least one SP CSI setting,the correction value to the first value (e.g., zero) for an initialtransmission (or a first transmission occasion) 2761 of the at least oneSP CSI report, for example, after or in response to receiving the firstMAC CE 2751.

The correction value may be set to a first value (e.g., zero) after orin response to receiving the first MAC CE 2751. The first value may beindependently determined regardless of a value of a TPC command in areceived DCI and may be independently determined regardless of thepresence or absence of the TPC command. Based on the first value, thewireless device 2720 may determine a transmit power of an initial SP CSIreport 2761 that is to be transmitted, to the base station 2710, afterreceiving the first MAC CE 2751. A transmit power of one or moresubsequent SP CSI reports 2762, 2763 may be determined based on thetransmit power of the SP CSI report 2761 and/or based on a value of atransmit power parameter of a received DCI.

FIG. 27 also shows an example of adjusting a correction value after orin response to receiving the second MAC CE 2752 deactivating the atleast one SP CSI (e.g., deactivating SP CSI reporting). The wirelessdevice 2720 may, based on one or more resource configuration parametersassociated with the at least one SP CSI setting, stop measuring SP CSIassociated with the at least one SP CSI setting and stop transmitting atleast one report of the measured SP CSI, for example, after or inresponse to receiving the second MAC CE 2752 indicating a deactivationof at least one SP CSI setting. The wireless device 2720 may determine acorrection value (or a TPC command) of an uplink transmit power for aPUCCH (e.g., for (control) data transmission via PUCCH), for example, ifthe at least one SP CSI setting has been deactivated. The correctionvalue may be transmitted via a DCI (e.g., L1 physical layer) scrambledby a particular RNTI (e.g., C RNTI). There may be no TPC command fordetermining an uplink transmit power of a first transmission 2771 (e.g.,an initial transmission or a first transmission occasion) via PUCCH (orPUSCH) after the at least one SP CSI setting is deactivated, forexample, if the wireless device 2720 deactivates the at least one SP CSIsetting. The wireless device 2720 may set the correction value to asecond value (e.g., zero) for the first transmission 2771, for example,after or in response to determining that no TPC command has beendetected for the first transmission 2771. There may be a TPC commandthat the wireless device 2720 may use to determine an uplink transmitpower for the first transmission 2771 (e.g., an initial transmission ofthe at least one report), for example, if the wireless devicedeactivates the at least one SP CSI setting. For example, the wirelessdevice 2720 may receive, at slot (e.g., mini-slot, subframe, or TTI)i-K_(PUCCH), a first DCI (e.g., a DCI comprising an uplink grant and/ora DCI comprising one or more TPC commands, e.g., format 2_2) comprisinga field indicating a first TPC command for a transmission at slot(mini-slot, subframe, or TTI) i. The transmission at slot (e.g.,mini-slot, subframe, or TTI) i may be scheduled (granted, or configured)for the at least one SP CSI setting. The first DCI may be scrambled by afirst RNTI (e.g., SP CSI RNTI) for the at least one SP CSI setting,and/or the first DCI may be scrambled by a second RNTI (e.g., C RNTI).

The physical layer of the wireless device 2720 may not have informationabout when the transmission of the at least one report over PUCCH willbe deactivated by the MAC layer, for example, if the transmission of theSP CSI report is deactivated by a MAC CE (e.g., the second MAC CE 2752).A first TPC command in a second DCI (e.g., comprising an uplink grantand a TPC command and/or DCI format 2_2 scrambled with a particular RNTI(TPC-PUCCH-RNTI)) that is detected by the wireless device 2720 may notbe used for the first transmission 2771. The wireless device 2720 mayignore the first TPC command received via the second DCI fortransmitting the first transmission 2771, for example, after or inresponse to receiving the second MAC CE 2752 indicating a deactivationof a transmission of at least one SP CSI report (e.g., deactivation ofSP CSI reporting). The wireless device 2720 may set the correction valueto a second value (e.g., zero) that may be predefined and/orsemi-statically configured, for example, instead of using the value ofthe first TPC command of the second DCI. For example, the wirelessdevice 2720 may, based on an indication of deactivating the at least oneSP CSI setting, set the correction value to the second value (e.g.,zero) for the first transmission 2771, for example, after or in responseto receiving the second MAC CE 2752. The correction value may be set toa second value (e.g., zero). The second value may be independentlydetermined regardless of the TPC command in a received DCI and may beindependently determined regardless of the presence or absence of theTPC command.

A wireless device (e.g., the wireless device 2720) may receive, from abase station (e.g., the base station 2710), at least one messagecomprising at least one of: one or more power control parameters for atransmission of at least one SP CSI report; at least one secondparameter indicating at least one SP CSI resource setting of the atleast one SP CSI report; at least one third parameter indicating atleast one SP CSI report setting of the at least one SP CSI report;and/or at least one forth parameter indicating at least one SP CSImeasurement setting of the at least one SP CSI report. For example, thewireless device may receive the first MAC CE 2751 indicating anactivation of a transmission of at least one SP CSI report (e.g.,activation of SP CSI reporting). After receiving the first MAC CE 2751,the wireless device may determine first transmission power for thestarting (or initial) transmission 2761 of the at least one SP-CSIreport 2761, 2762, 2763 at least based on: the one or more power controlparameters and/or at least one correction value being set to apredefined value (e.g., zero). The first transmission power for thestarting transmission 2761 may be determined, for example, after or inresponse to the first MAC CE 2751 indicating the activation. Thewireless device may transmit the at least one SP CSI report 2761, 2762,2763 via a PUCCH (or PUSCH) based on the first transmission power (e.g.,the first transmission power may correspond to the transmission power ofthe PUCCH comprising the at least one SP CSI report 2761, 2762, 2763).

The wireless device may receive the second MAC CE 2752 indicating adeactivation of at least one SP CSI report 2761, 2762, 2763 (e.g.,deactivation of SP CSI reporting). The wireless device may determine atleast one correction value being set to a predefined value (e.g., zero),for example, after or in response to receiving the second MAC CE 2752.

The physical layer of the wireless device may not have information aboutwhen the transmission of the at least one SP CSI report setting overPUCCH will be activated or deactivated by the MAC layer, for example, ifthe transmission is activated or deactivated by a MAC CE (e.g., due to aretransmission (HARM)). It may be unclear for the physical layer when tostart PDCCH monitoring with a first DCI (e.g., indicating an activationor a deactivation of SP CSI) scrambled by a first RNTI (e.g., SP CSIRNTI) and/or with a second DCI (e.g., indicating a PUCCH TPC command)scrambled by a second RNTI (e.g., C-RNTI and/or TPC-PUCCH-RNTI). Thefirst DCI may be associated with the at least one SP CSI report setting(e.g., activation or a deactivation of at least one SP CSI reportsetting), and the second DCI may not be associated with the at least oneSP CSI report setting. The wireless device may start monitoring for aPDCCH to obtain the first DCI, for example, if the at least one SP CSIreport setting is activated by a MAC CE (e.g., the first MAC CE 2751).For example, after receiving the first MAC CE 2751, the wireless devicemay receive one or more PDCCHs and may detect the first DCI comprised inat least one of the one or more PDCCHs. The wireless device may startmonitoring for a PDCCH to obtain the second DCI and may not monitor forthe PDCCH for the first DCI, for example, if the at least one SP CSIreport setting is deactivated by a MAC CE (e.g., the second MAC CE2752). For example, after receiving the second MAC CE 2752, the wirelessdevice may receive one or more PDCCHs and may detect the second DCIcomprised in at least one of the one or more PDCCHs. A base station maytransmit the first DCI for adjusting an uplink transmit power of atleast one SP CSI report, for example, after or in response totransmitting the first MAC CE 2751 activating the at least one SP CSIreport setting associated with the at least one SP CSI report.

If the base station does not have information about whether the wirelessdevice has received the first MAC CE 2751 and/or when the wirelessdevice receives the first MAC CE 2751, the wireless device may be morelikely to miss the first DCI. The wireless device may be more likely tomiss the first DCI, for example, if the first DCI is transmitted whenthe wireless device is not prepared to monitor a PDCCH comprising thefirst DCI. The wireless device may not miss the first DCI, for example,if the base station transmits the first DCI with a delay that may belong enough for the wireless device to prepare the PDCCH monitoring forthe first DCI detection. The delay may be a delay between thetransmission of the first MAC CE 2751 and the transmission of the PDCCHcomprising the first DCI.

The delay may cause a latency problem and/or cause energy savingproblem. The wireless device may consume more energy for the PDCCHmonitoring, for example, if the wireless device is ready to monitor thePDCCH before the expiration of the delay. To indicate the reception ofthe MAC CE, the wireless device may transmit a confirmation to the basestation, for example, after or in response to receiving a MAC CEindicating an activation or deactivation of a configured SP CSI reportsetting.

FIG. 28A and FIG. 28B show examples of transmitting one or moreconfirmation messages indicating reception of a MAC CE activating ordeactivating (suspending or releasing) SP CSI. FIG. 28A and FIG. 28B maybe similar to each other, except for the different SP CSI reporttransmission periods (e.g., transmission windows) 2890A, 2890B. Awireless device 2820A, 2820B (e.g., a UE) may start monitoring for thePDCCH comprising the first DCI, for example, after or in response totransmitting a first confirmation message 2871A, 2871B (“firstconfirmation”). The first confirmation may be transmitted to a basestation 2810A, 2810B (e.g., a gNB), for example, after or in response toreceiving a first MAC CE 2851A, 2851B activating SP CSI. The basestation 2810A, 2810B may transmit, to the wireless device 2820A, 2820Band after receiving the first confirmation, the PDCCH comprising thefirst DCI. The PDCCH comprising the first DCI may be transmitted one ormore times during the one or more SP CSI report transmission periods2890A, 2890B. The first confirmation may be transmitted, for example,after or in response to receiving the first MAC CE 2851A, 2851Bindicating an activation of at least one SP CSI report setting.

The wireless device 2820A, 2820B may transmit, to the base station2810A, 2810B, a second confirmation message 2872A, 2872B (“a secondconfirmation”), for example, after or in response to receiving a secondMAC CE 2852A, 2852B deactivating the SP CSI. The wireless device 2820A,2820B may stop the monitoring for the PDCCH comprising the first DCI,for example, after or in response to receiving the second MAC CE 2852Aindicating a deactivation of at least one SP CSI report setting (e.g.,in FIG. 28A). The wireless device 2820A, 2820B may stop the monitoringfor the PDCCH comprising the first DCI, for example, after or inresponse to transmitting a second confirmation message 2872B (e.g., inFIG. 28B). The second confirmation message 2872B may be transmitted, forexample, after or in response to receiving the second MAC CE 2852B. Atleast one of the first or the second confirmation may be transmitted viaa UL MAC PDU (e.g., MAC CE). At least one LCID may be assigned for thefirst and/or second confirmation.

FIG. 29 shows an example of adjusting a correction value associated witha transmit power determination. A base station 2910 (e.g., a gNB) mayestablish an RRC connection with a wireless device 2920 (e.g., a UE).For example, the base station 2910 may transmit, to the wireless device2920, one or more higher layer parameters (e.g., parameters of an RRClayer) to establish the RRC connection. The base station 2910 maytransmit, to the wireless device 2920, one or more PDCCHs comprisingcontrol information (e.g., one or more DCIs). The wireless device 2920may transmit, to the base station 2910, uplink data (e.g., UL-SCH data).The uplink data may be mapped to one or more PUSCH resources assigned tothe wireless device 2920. The one or more PUSCH resources may beassigned by control information transmitted from the base station 2910.

The wireless device 2920 may transmit, to the base station 2910, one ormore PUSCHs comprising uplink data (e.g., UL-SCH data), for example,before receiving a first message 2951 activating SP CSI. The firstmessage 2951 may have at least one of a plurality formats (e.g., a MACCE, a DCI, etc.). The wireless device 2920 may determine, based on oneor more power parameters, transmit power of each PUSCH transmission. Asdescribed above, a wireless device's transmit power P_(PUSCH,c)(i) forPUSCH transmission in a subframe (TTI, slot, and/or mini-slot) i for theserving cell c may be given by

${{P_{{PUSCH},c}(i)} = {\min {\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{O\; \_ \; {PUSCH}}(j)} +} \\{{{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}},$

for example, if the wireless device 2920 transmits the PUSCH without asimultaneous PUCCH on a carrier f of the serving cell c. Other equationsand/or methods described herein may also be used to determine thewireless device's transmit power.

P_(O) _(_) _(PUSCH,c)(j) may have different values for datatransmissions and SP CSI transmissions on PUSCH. For example, for thetransmission of UL-SCH data on PUSCH, P_(O) _(_) _(PUSCH,c)(j) may havea first value, and for the transmission of an SP CSI on PUSCH, P_(O)_(_) _(PUSCH,c)(J) may have a second value different from the firstvalue.

A correction value (e.g., δ_(PUSCH,c)) may be provided from the basestation 2910. For example, a TPC command in a DCI may indicate thecorrection value. As described above, the wireless device 2920 may setf_(c)(i)=δ_(PUSCH,c)(i−K_(PUSCH)) andf_(c,2)(i)=δ_(PUSCH,c)(i−K_(PUSCH)), for example, if accumulation may benot enabled for serving cell c based on the parameter (e.g.,Accumulation-enabled) provided by higher layers.δ_(PUSCH,c)(i−K_(PUSCH)) may be signaled on a PDCCH/EPDCCH with a DCI(e.g., DCI format 0/0A/0B/4/4A/4B) or an MPDCCH with a DCI (e.g., DCIformat 6-0A) for the serving cell c on a subframe (TTI, slot, and/ormini-slot) i−K_(PUSCH).

As described above, a wireless device (e.g., the wireless device 2920)may set f_(c)(i)=f_(c)(i−1), for example, if the wireless device isconfigured with a higher layer parameter (e.g.,UplinkPowerControlDedicated) for the serving cell c and if the subframe(TTI, slot, and/or mini-slot) i belongs to an uplink power controlsubframe (TTI, slot, and/or mini-slot) set 2 as indicated by the higherlayer parameter (e.g., tpc-SubframeSet).

The wireless device may set f_(c,2)(i)=f_(c,2)(i−1), for example, if thewireless device is configured with a higher layer parameter (e.g.,UplinkPowerControlDedicated) for the serving cell c and if the subframe(TTI, slot, and/or mini-slot) i does not belong to an uplink powercontrol subframe (TTI, slot, and/or mini-slot) set 2 as indicated by thehigher layer parameter tpc-SubframeSet.

f_(c,2)(i) and f_(c)(i) may be defined by:f_(c)(i)=f_(c)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH)) andf_(c,2)(i)=f_(c,2)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH)), for example, ifaccumulation may be enabled based on the parameter (e.g.,Accumulation-enabled) provided by higher layers and/or if the TPCcommand δ_(PUSCH,c) may be included in a PDCCH/EPDCCH with a DCI format(e.g., DCI format 0 in LTE and/or DCI format 0_0/0_1/2_2 in NR) or in anMPDCCH with a DCI format (e.g., DCI format 6-0A) for the serving cell c,where the CRC may be scrambled by the Temporary C-RNTI. For example, theMO value for the current transmission of UL-SCH data on a PUSCH may bedetermined by adding the δ_(PUSCH,c) value to the f_(c)(i−1) value(e.g., f_(c)(i−1) may be the f_(c)(i) value of the previous transmissionof the UL-SCH data on PUSCH).

At least one of the δ_(PUSCH,c) or the f_(c)(i) may be changed (e.g.,initialized or reset), for example, after or in response to receivingthe first message 2951. The wireless device 2920 may transmit the firstdata 2971 on a PUSCH, for example, after receiving the first message2951. For the transmit power of the transmission of the first data 2971,the wireless device 2920 may set at least one of the δ_(PUSCH,c) or thef_(c)(i) to predefined values (e.g., a first value). For example,f_(c)(i) may be set to f_(c)(0)=0, and δ_(PUSCH,c) may be set to thefirst value (e.g., zero). The f_(c)(i) value used for the transmissionof the data 2971 may be used as the f_(c)(i−1) value for the first SPCSI report 2961 to calculate the f_(c)(i) value for the transmit powerof the first SP CSI report 2961.

A first DCI 2981 may indicate a change of the δ_(PUSCH,c) value. Forexample, a TPC command field in the first DCI 2981 may indicate thechanged value for the δ_(PUSCH,c) which may be used for the transmitpower calculation for the transmission of the next SPC CSI report 2962.The f_(c)(i) value used for the transmission of the previous PUSCHtransmission (e.g., a data transmission between the SP CSI report 2961and the SP CSI report 2962) may be used as the f_(c)(i−1) value for thesecond SP CSI report 2962 to calculate the f_(c)(i) value for thetransmit power of the second SP CSI report 2962.

At least one of the δ_(PUSCH,c) or the f_(c)(i) may be changed (e.g.,initialized or reset), for example, after or in response to receivingthe second message 2952 deactivating (suspending or releasing) the SPCSI. After receiving the second message 2952, the wireless device 2920may transmit the data 2972 on a PUSCH. For the transmit power of thetransmission of the data 2972, the wireless device 2920 may set at leastone of the δ_(PUSCH,c) or the f_(c)(i) to predefined values (e.g., asecond value). For example, f_(c)(i) may be set to f_(c)(0)=0, andδ_(PUSCH,c) may be set to the second value (e.g., zero). The f_(c)(i)value used for the transmission of the data 2972 may be used as thef_(c)(i−1) value for an immediately subsequent transmission on a PUSCHto calculate the f_(c)(i) value for the transmit power of theimmediately subsequent transmission on the PUSCH. A second DCI 2982 maychange the δ_(PUSCH,c) value for the immediately subsequent transmissionon PUSCH.

FIG. 30 shows an example of an SP CSI activation procedure that may beperformed by a base station. At step 3002, the base station maydetermine an activation of SP CSI for one or more wireless devices. Forthe activation of SP CSI (e.g., activation of SP CSI reporting) for awireless device, the base station may determine to send, to the wirelessdevice, an indication that the base station will activate the SP CSI,that the base station will send one or more SP CSI-RSs after theactivation, and that the base station will receive, from the wirelessdevice, one or more SP CSI reports. The wireless device may generate theone or more SP CSI reports by measuring the one or more SP CSI-RSs. Thedetermination at step 3002 may be based on one or more parameters,factors, and/or conditions. The base station may determine to activatethe SP CSI for the wireless device, for example, if a channel conditionbetween the base station and the wireless device is not consistentand/or if the channel monitoring using the SP CSI is preferred.

At step 3004, the base station may determine an uplink channel via whichthe base station will receive the one or more SP CSI reports. Forexample, the base station may determine an uplink control channel (e.g.,PUCCH), an uplink shared channel (e.g., PUSCH), and/or other channels toreceive the one or more SP CSI reports. The determination at step 3004may be based on one or more parameters, factors, and/or conditions. Forexample, resource availability may affect the determination between theuplink control channel and the uplink shared channel. The base stationmay determine to receive the one or more SP CSI reports via an uplinkshared channel, for example, if available resources in uplink controlchannels are scarce. The determination between the uplink controlchannel and the uplink shared channel may be based on the periodicity ofSP CSI report transmissions (e.g., the time interval between twoadjacent SP CSI report transmissions). The base station may determine toreceive the SP CSI reports via an uplink control channel, for example,if the time interval is longer than a threshold interval (e.g., thewireless device does not use the uplink control channel very frequentlyto transmit the SP CSI reports because the time interval is long).

At step 3006, the base station may transmit, to the wireless device, aMAC CE indicating the activation of SP CSI (e.g., activation of SP CSIreporting), for example, if the base station determines to receive theone or more SP CSI reports via the uplink control channel. For example,the selection of the MAC CE for the SP CSI activation indication mayimplicitly indicate that the one or more SP CSI reports should bereported via an uplink control channel. At step 3008, the base stationmay transmit, to the wireless device, a DCI indicating the activation ofSP CSI (e.g., activation of SP CSI reporting), for example, if the basestation determines to receive the one or more SP CSI reports via theuplink shared channel. For example, the selection of the DCI for the SPCSI activation indication may implicitly indicate that the one or moreSP CSI reports should be reported via an uplink shared channel.

For the deactivation of SP CSI (e.g., deactivation of SP CSI reporting)for the wireless device, the base station may send a same type ofmessage (e.g., a MAC CE) indicating the deactivation of SP CSI, forexample, if the base station previous sent the same type of message(e.g., a MAC CE) indicating the activation of SP CSI.

FIG. 31 shows an example of an SP CSI reporting procedure that may beperformed by a wireless device. At step 3102, the wireless device mayreceive a control message indicating an activation of SP CSI. Forexample, the wireless device may receive, from a base station, a MAC CEor DCI indicating the activation of SP CSI. The wireless device mayreceive, from the base station, one or more SP CSI-RSs. The wirelessdevice may measure the one or more SP CSI-RSs. At step 3104, thewireless device may schedule a transmission of one or more SP CSIreports. For example, the wireless device may measure SP CSI-RSs and maygenerate, based on the measurements, the one or more SP CSI reports. Totransmit the one or more SP CSI reports, one or more PUSCH resources maybe determined. At step 3106, the wireless device may determine, based ona changed correction value, uplink transmit power of the transmission ofthe one or more SP CSI reports. For example, the changed correctionvalue may be used to determine the transmit power of the first SP CSIreport that is to be transmitted after the SP CSI activation. At step3108, the wireless device may transmit, based on the uplink transmitpower, the one or more SP CSI reports. For example, the wireless devicemay use the uplink transmit power to set the transmit power for thetransmission of the PUSCH comprising the one or more SP CSI reports.

A base station may send, to a wireless device, at least one messagecomprising configuration parameters to establish a wireless connection(e.g., an RRC connection). One or more of the configuration parametersmay be provided via higher layer signaling (e.g., an RRC message). Theconfiguration parameters may comprise information of SP CSI-RS,information of one or more SP CSI reports, etc. The at least one messagemay comprise one or more uplink power control parameters associated withan uplink channel transmission (e.g., PUCCH, PUSCH, etc.) The one ormore power control parameters may be associated with the one or more SPCSI reports, for example, if the one or more SP CSI reports arecomprised in (e.g., mapped on) the uplink channel and sent to the basestation. The at least one message may comprise an RNTI (e.g., SP-CSIC-RNTI) that is associated with the SP CSI reports. The base station maysend a control message indicating an activation of one or more SP CSIreports (e.g., activation of SP CSI reporting). The control message mayindicate that the base station will start to send, to the wirelessdevice, one or more SP CSI-RSs via one or more downlink channels (e.g.,PDCCH, PDSCH, etc.). The control message may request that the wirelessdevice measure the one or more SP CSI-RSs and that the wireless devicesend, to the base station and via one or more uplink channels, the oneor more SP CSI reports. The control message may comprise a first fieldand a second field. The first field may indicate a logical channelidentifier that indicates whether the control message is used toactivate or deactivate one or more SP CSI reports (e.g., activation ordeactivation of SP CSI reporting). For example, the first field mayindicate that the control message is a message type for SP CSIactivation or deactivation. The second field may indicate whether thecontrol message indicates the activation or a deactivation. For example,the second field may have a first value (e.g., one) that indicates theactivation of SP CSI reports or may have a second value (e.g., zero)that indicates the deactivation of SP CSI reports. The control messagemay comprise a DCI scrambled by the RNTI that is associated with the SPCSI reports. The wireless device may receive a PDCCH comprising the DCIfrom the base station. The wireless device may determine, based on theRNTI and the DCI, the indication of activation. For example, thewireless device may decode, based on the RNTI, the PDCCH and maydetermine, from the DCI, the indication of activation. The wirelessdevice may validate, based on a plurality of fields in the DCI, theactivation. The base station may indicate one or more downlinktime-frequency resources (e.g., PDCCH or PDSCH mapped on particularresource elements) in which the one or more SP CSI-RSs are to be sent.The base station may indicate one or more uplink time-frequencyresources (e.g., PUCCH or PUSCH mapped on particular resource elements)in which the one or more SP CSI reports are to be sent. The controlmessage may be a DCI, a MAC CE, etc. The wireless device may determine atransmission power for a transmission of at least one of the one or moreSP CSI reports. The transmission power may be determined, for example,based on the one or more uplink power control parameters and/or at leastone correction value adjusted based on the activation of one or more SPCSI reports. The wireless device may adjust (e.g., change, set, reset,or initialize) the at least one correction value to a first value (e.g.,zero), for example, after or in response to receiving the controlmessage. The wireless device may send, to the base station and based onthe transmission power, at least one of the one or more SP CSI reports.

The base station may send, to the wireless device, a second controlmessage indicating a deactivation of one or more SP CSI reports (e.g.,deactivation of SP CSI reporting). The second control message may be aDCI, a MAC CE, etc. The second control message may comprise a second DCIscrambled by the RNTI that is associated with the SP CSI reports. Thesecond control message may comprise a first field and a second field.The first field may indicate a logical channel identifier that indicateswhether the control message is used to activate or deactivate one ormore SP CSI reports. For example, the first field may indicate that thesecond control message is a message type for SP CSI activation ordeactivation. The second field may indicate whether the second controlmessage indicates the activation or the deactivation. For example, thesecond field may have a first value (e.g., one) that indicates theactivation of SP CSI reports (e.g., activation of SP CSI reporting) ormay have a second value (e.g., zero) that indicates the deactivation ofSP CSI reports (e.g., deactivation of SP CSI reporting). The wirelessdevice may receive a second PDCCH comprising the second DCI from thebase station. The wireless device may determine, based on the RNTI andthe second DCI, the indication of deactivation. For example, thewireless device may decode, based on the RNTI, the second PDCCH and maydetermine, from the second DCI, the indication of deactivation. Thesecond control message may indicate that the wireless device is no morerequired to perform the measurement of the SP CSI-RSs and/or thetransmission of the SP CSI reports. The wireless device may adjust(e.g., change, set, reset, or initialize) the at least one correctionvalue to a second value (e.g., zero), for example, after or in responseto receiving the second control message. The wireless device mayschedule a second transmission, of uplink information (e.g., UL SCHdata), that is after receiving the second control message. The wirelessdevice may determine, based on the at least one correction value beingadjusted to the second value, a second transmission power for the secondtransmission. The wireless device may send, based on the secondtransmission power, the uplink information. The base station may send,to the wireless device, a third DCI comprising an uplink grant for atransmission of at least one transport block. The wireless device maydetermine a third transmission power of the transmission of at least onetransport block. The third transmission power may be determined based onthe at least one correction value being set to a value (e.g., the firstvalue, the second value, or a third value). The wireless device maysend, to the base station and via one or more resources indicated by theuplink grant, the at least one transport block.

A base station may send, to a wireless device, at least one controlmessage. The control message may comprise at least one of a firstindication of activating one or more semi-persistent channel stateinformation reports or a second indication of deactivating one or moresemi-persistent channel state information reports. The wireless devicemay adjust, based on at least one of the first indication or the secondindication, at least one correction value associated with a transmissionpower of a transmission of uplink information. The wireless device maydetermine, based on the adjusted at least one correction value, thetransmission power. The wireless device may send, via an uplink channeland based on the transmission power, the uplink information. The uplinkinformation may comprise one or more of: the one or more semi-persistentchannel state information reports; or one or more uplink shared channeldata. The at least one control message may comprise a first fieldindicating a logical channel identifier that indicates whether thecontrol message is used to activate or deactivate the one or moresemi-persistent channel state information reports. The at least onecontrol message may comprise a second field indicating whether thecontrol message indicates the activating of the one or moresemi-persistent channel state information reports. The base station maysend, to the wireless device, a radio network temporary identifierassociated with the one or more semi-persistent channel stateinformation reports. The wireless device may adjust the at least onecorrection value (e.g., by setting, based on the first indication, theat least one correction value to a first value or by setting, based onthe second indication, the at least one correction value to a secondvalue).

A MAC CE may be transmitted as a part of a MAC PDU. The MAC PDU may be abit string that may be byte aligned (e.g., one or more of 8 bits) inlength. The MAC PDU may comprise at least one of at least one MACsubheader, at least one MAC SDU, or at least one MAC CE.

FIG. 32A, FIG. 32B and FIG. 32C show examples of MAC subheaders 3200A,3200B, 3200C, respectively. The MAC subheader 3200A may be an example ofa first type of R/F/LCID/L MAC subheader with 8-bit L field, the MACsubheader 3200B may be an example of a second type of R/F/LCID/L MACsubheader with 16-bit L field, and the MAC subheader 3200C may be anexample of R/LCID MAC subheader.

FIG. 33A shows an example of a MAC PDU for a DL MAC PDU, and FIG. 33Bshows an example of a MAC PDU for a UL MAC PDU. A bit order of one ormore parameter fields within a MAC PDU may be represented with the firstand most significant bit (MSB) in the leftmost bit and the last and LSBin the rightmost bit.

A MAC SDU may be a bit string that may be byte aligned (e.g., one ormore of 8 bits) in length. The MAC PDU may comprise a MAC SDU from thefirst bit onward. A MAC CE may be a bit string that may be byte aligned(e.g., one or more of 8 bits) in length. A MAC subheader may be a bitstring that may be byte aligned (e.g., one or more of 8 bits) in length.A MAC subheader may be placed in front of the corresponding MAC SDU, MACCE, or padding. A wireless device may ignore a value of one or moreReserved bits (e.g., “R” fields in FIGS. 32A, 32B, and 32C) in downlinkMAC PDUs.

A MAC PDU may comprise one or more MAC subPDUs. At least one of the oneor more MAC subPDUs may comprise at least one of the following: a MACsubheader only (including padding); a MAC subheader and a MAC SDU; a MACsubheader and a MAC CE; and/or a MAC subheader and padding.

The MAC SDUs may have variable sizes. A MAC subheader may correspond toeither a MAC SDU, a MAC CE, or padding. A MAC subheader for one or moreportions of a MAC PDU, except for a fixed-sized MAC CE and padding, maycomprise at least four header fields R/F/LCID/L. A MAC subheader for afixed-sized MAC CE and padding may comprise at least two header fieldsR/LCID.

One or more MAC CEs may be placed together. One or more DL MAC subPDUscomprising one or more MAC CEs may be placed before a MAC subPDUcomprising a MAC SDU and before a MAC subPDU comprising padding (e.g.,as shown in FIG. 33A).

One or more UL MAC subPDUs comprising one or more MAC CEs may be placedafter one or more (e.g., all) MAC subPDUs comprising a MAC SDU andbefore a MAC subPDU comprising padding (e.g., as shown in FIG. 33B). Thesize of padding may be zero.

At least one set of one or more SP CSI report settings for a PUCCH (orPUSCH) may be RRC configured (e.g., by a base station). For example, fora wireless device, at least one of the one or more SP CSI reportsettings for a PUCCH may be configured in RRC with one or more PUCCHresources for transmitting one or more SP CSI reports. A transmission ofthe one or more SP CSI reports via the one or more PUCCH resources maybe activated by a MAC CE. The MAC CE may comprise at least one logicalchannel ID (LCID) indicating whether the MAC CE is for an activationand/or deactivation of SP CSI. The MAC CE may comprise an LCID assignedto indicate an activation and/or deactivation with at least one fieldindicating whether the MAC CE is for an activation and/or deactivation.For example, at least two LCIDs may be respectively assigned to anactivation (e.g., that may be indicated by a first LCID) or deactivation(e.g., that may be indicated by a second LCID). The MAC CE may compriseone or more fields indicating at least one of the following: at leastone SP CSI report setting, at least one SP CSI resource setting, and/orat least one SP CSI measurement setting. The MAC CE may be used toactivate or deactivate (release or suspend) the one or more PUCCHresources (and/or PUSCH resources) scheduled (configured, or granted)for a transmission of the at least one SP CSI report.

The wireless device may start measuring SP CSI and transmit the SP CSIreport, based on at least one SP CSI setting, for example, after or inresponse to receiving a first MAC CE indicating an activation of atleast one SP CSI report transmitted via a PUCCH (or PUSCH). The at leastone SP CSI setting may be associated with the at least one SP CSI reportand may comprise at least one of the following: at least one SP CSIreport setting, at least one SP CSI resource setting, and/or at leastone SP CSI measurement setting. The wireless device may receive a secondMAC CE indicating a deactivation of at least one SP CSI report (e.g.,deactivation of SP CSI reporting). The wireless device may deactivate atransmission of at least one SP CSI report, for example, after or inresponse to receiving the second MAC CE. The wireless device may release(or suspend) one or more downlink assignments of SP CSI and/or one ormore PUCCH resources scheduled (configured, or granted) for thetransmission of the at least one SP CSI report, for example, after or inresponse to receiving the second MAC CE.

The at least one SP CSI setting may be indicated by the first and/or thesecond MAC CE. The first and/or second MAC CE may comprise at least oneselection command indicating at least one CSI reporting settingindication. The first and/or the second MAC CE may comprise one or moreindices indicating the at least one SP CSI setting. The one or moreindices may comprise at least one of the following: a first indexindicating one of at least one SP CSI report setting, a second indexindicating one of at least one SP CSI resource setting, and/or a thirdindex indicating one of at least one SP CSI measurement setting. The atleast one SP CSI setting may be semi-statically configured by RRC.

A base station (e.g., a gNB) may configure a wireless device (e.g., aUE) with at least one SP CSI setting. The base station may transmit, tothe wireless device, a DCI scrambled by an RNTI for SP CSI (e.g., SP CSIRNTI), or a MAC CE, that indicates an activation of at least one SP CSIsetting (e.g., activation of SP CSI reporting). The wireless device maytransmit a first UCI comprising at least one SP CSI report in a firsttime occupancy of a physical channel (TTI, slot, mini-slot, or subframe)via PUSCH or PUCCH. The at least one SP CSI report may be associatedwith the at least one SP CSI setting. The first UCI may be transmittedvia a PUSCH, for example, if the at least one SP CSI setting isactivated by a DCI. The first UCI may be transmitted via a PUCCH, forexample, if the at least one SP CSI setting is activated by a MAC CE.

The wireless device may transmit the first UCI without data (e.g.transmit the first UCI without UL-SCH data), for example, if the firstUCI, comprising at least one SP CSI report, is transmitted via a PUSCH.The data (e.g., UL-SCH data) may not be transmitted via the PUSCH, forexample, if there is no uplink grant for the PUSCH in a second timeoccupancy of the physical channel (TTI, slot, mini-slot, or subframe)The first time occupancy scheduled to carry at least one SP CSI reportmay not be overlapped in at least a first portion of the second timeoccupancy, the second time occupancy may not start within a first timeinterval (a first value of time, or a first value of time window) afterthe termination of the first time occupancy, or the first time occupancymay not start within the first time interval after the termination ofthe second time occupancy. The wireless device may transmit the firstUCI with data (e.g. UL-SCH data), for example, if the wireless devicehave the data with an uplink grant (e.g., dynamic, configured, and/orsemi-persistent grant) to transmit via a PUSCH in a third time occupancyof the physical channel (TTI, slot, mini-slot, or subframe). The firsttime occupancy may be overlapped in at least a first portion of thethird time occupancy, the third time occupancy may start within a firsttime interval after the termination of the first time occupancy, or thefirst time occupancy may start within the first time interval after thetermination of the third time occupancy. The first portion and/or thefirst time interval may be predefined, for example, in terms of severalmicroseconds or milliseconds, at least one OFDM symbol, one or more OFDMsymbols, a portion of one OFDM symbol, and/or one or more TTIs (slots,mini-slot, or subframe).

FIG. 34A shows an example of SP CSI piggybacking on a PUSCH 3410A, forexample, if an SP CSI transmission schedule is at least partiallyoverlapped in time with a PUSCH data transmission schedule. FIG. 34Bshows an example of SP CSI piggybacking on a PUSCH 3410B, for example,if a PUSCH data transmission is scheduled to start within a firstinterval after a scheduled termination of an SP CSI transmission. Awireless device may transmit a UCI via PUCCH or PUSCH in parallel withdata (e.g., UL SCH) via a PUSCH. The UCI may comprise at least one SPCSI report. The wireless device may have a performance loss, forexample, if the UCI is transmitted with data in parallel For example,the performance loss may be due to a limited hardware capability. Forexample, peak-to-average power (PAPR) ratio, inter-modulation distortion(IMD), out-of-band (OOB) leakage, and/or reduction in power capability(cubic metric (CM) problem) may occur or exacerbate the performanceloss, for example, if data transmission and UCI transmission areperformed in parallel.

A wireless device may transmit a UCI, comprising at least one SP CSIreport, through a piggybacking on a PUSCH (e.g., PUSCHs 3410A, 3410B) toreduce or avoid the performance loss. For example, the UCI may bepiggybacked on the PUSCH data transmission, for example, iftransmissions of the PUSCH and the SP CSI report are scheduled fortransmission in parallel. The transmissions of the PUSCH and the SP CSImay be in parallel, for example, if 1) the transmissions of the UCI anddata are scheduled on a PUCCH (or a first PUSCH) and a second PUSCH,respectively, and at least a portion of the transmissions of the PUCCH(or the first PUSCH) and the second PUSCH are scheduled to overlap intime (e.g., as shown in FIG. 34A), 2) the transmission of the PUSCH fordata is scheduled to start within the first time interval after ascheduled termination of the SP CSI transmission (e.g., as shown in FIG.34B), or 3) the transmission of the SP CSI is scheduled to start withinthe first time interval after a scheduled termination of the PUSCH datatransmission. The UCI may be piggybacked on the PUSCH for a datatransmission, for example, if transmissions of the UCI and data via thePUSCH are scheduled for transmission in parallel. The UCI and data maybe scheduled for transmission in parallel, for example, if at least aportion of the transmissions of the UCI and data on the PUSCH areoverlapped in time, the transmission of the data on the PUSCH isscheduled within a first time interval after a scheduled termination ofthe transmission of the UCI, or the transmission of the UCI is scheduledwithin a first time interval after a scheduled termination of thetransmission of the data on the PUSCH. The first portion and/or thefirst time interval may be predefined, for example, in terms of severalmicroseconds or milliseconds, one or more OFDM symbols, a portion of oneOFDM symbol, and/or one or more TTIs (slots, mini-slot, or subframe).

The wireless device may determine, based on a type of UCI, whetherand/or when the UCI is piggybacked on the PUSCH for a data transmission.The UCI may comprise ACK/NACK. The ACK/NACK may be configured to betransmitted to a base station in a predetermined time interval. Forexample, if the wireless device receives data (e.g., via PDCCH and/orPDSCH) in an ith TTI (slot, mini-slot, or subframe), the UCI withACK/NACK corresponding to the data may be configured to be transmittedin an (i+x)th TTI (slot, mini-slot, or subframe) (e.g., the interval xmay be predefined, for example, x=1, 2, 4, or 8). The UCI may compriseat least one of periodic and/or SP CSIs. The CSIs may comprise one ormore values indicating at least one of CQI, PMI, RI, etc. A TTI (e.g.,slot, mini-slot, or subframe), in which the UCI may be transmitted, maybe determined, based on a period and/or an offset semi-staticallyconfigured by higher layer signaling, for example, if the UCI isperiodic and/or semi-persistent.

Based on the type of UCI, the wireless device may determine a channelallocation for UCI piggybacking on a PUSCH. The wireless device mayallocate and transmit the UCI to the PUCCH or PUSCH through the channelallocation procedure.

One or more uplink power control parameters may be predefined and/orsemi-statically configured for a transmission of SP CSI on a PUSCH.P_(O) _(_) _(PUSCH,f,c)(j) and α_(f,c)(j) for the transmission of SP CSI(or UCI) may be predefined and/or semi-statically configured for acarrier f of a cell c, where j∈{0,1,2, . . . , J−1}=S_(J). P_(O) _(_)_(PUSCH,f,c)(j_(SPCSI)) and α_(f,c)(j_(SPCSI)) (where j_(SPCSI)∈S_(J))may be for the transmission of SP CSI (or UCI) on PUSCH. P_(O) _(_)_(PUSCH,f,c)(j_(data)) and α_(f,c)(j_(data)) (where j_(data)∈S_(J)) maybe for the transmission of data on a PUSCH. P_(O) _(_) _(PUSCH,f,c)(j)and α_(f,c)(j) values may be provided by a set of higher layerparameters (e.g., p0-pusch-alpha-set) and a respective index by higherlayer parameter (e.g., p0alphasetindex) for the carrier f of the cell c.The size of the set may be J−2 and may be indicated by higher layerparameter (e.g., num-p0-alpha-sets).

One or more uplink power control parameters may be predefined and/orsemi-statically configured for a transmission of SP CSI on a PUCCH (orPUSCH). P_(O) _(_) _(PUCCH,f,c)(q_(u)) for the transmission of SP CSI(or UCI) may be predefined and/or semi-statically configured for acarrier f of a cell c. P_(O) _(_) _(PUCCH,f,c)(q_(u)) may comprise P_(O)_(_) _(UE) _(_) _(PUCCH)(q_(u)) for 0≤q_(u)<Q_(u). P_(O) _(_) _(UE) _(_)_(PUCCH)(q_(SPCSI)) (and/or P_(O) _(_) _(UE) _(_) _(PUCCH)(q_(SPCSI))may be for the transmission of SP CSI (or UCI) on a PUCCH, where0≤q_(SPCSI)<Q_(u). P_(O) _(_) _(PUCCH,f,c)(q_(SPCSI)) (and/or P_(O) _(_)_(UE) _(_) _(PUCCH)(q_(SPCSI))) may be provided by a set of higher layerparameters (e.g., P0-PUCCH). Q_(u) may be a size for a set of P_(O) _(_)_(UE) _(_) _(PUCCH)(q_(u)) values provided by higher layer parameternum-p0-pucch. The set of P_(O) _(_) _(UE) _(_) _(PUCCH)(q_(u)) valuesmay be provided by higher layer parameter p0-pucch-set.

One or more values of uplink power control parameters (e.g., P_(O) _(_)_(PUSCH,f,c)(j_(SPCSI)), α_(f,c)(j_(SPCSI)), P_(O) _(_)_(PUCCH,f,c)(q_(SPCSI)), and/or P_(O) _(_) _(UE) _(_)_(PUCCH)(q_(SPCSI))) for SP CSI may be semi-statically configured basedon one or more requirements and/or channel condition of a UCI (e.g., SPCSI) transmission, for example, in terms of reliability (BLER, SNIR,SNR, etc.), number of bits transmitted in UCI, latency, etc.

The wireless device may need to determine which one of one or morevalues to be used for uplink transmit power of the UCI transmission, forexample, if a UCI comprising at least one SP CSI report is transmittedon a PUSCH. The UCI comprising at least one SP CSI scheduled on a PUCCHmay be piggybacked on a PUSCH. The UCI comprising at least one SP CSIscheduled on a PUSCH may be piggybacked on a PUSCH. The UCI may betransmitted with data. The UCI may be transmitted without data.

A selection of one or more wrong values for uplink transmit power mayresult in miscalculation of required uplink transmit power (e.g., linkbudget surplus/deficit). For example, the wireless device may consumemore power and/or the wireless device may perform a retransmission.

At least one value of uplink transmit power component for SP CSI onPUSCH may be used, for example, if a UCI comprising at least one SP CSIreport is transmitted via a PUSCH. The at least one value may besemi-statically configured based on one or more requirement of UCItransmission. The selection of the at least one value for the UCItransmission via a PUSCH may guarantee the one or more requirement of aUCI transmission. The at least one value may be larger than the one fora data transmission. Selecting the at least one value for the UCItransmission via PUSCH may increase the likelihood of success of the UCItransmission (e.g., high SNR/SINR, and/or low BLER). The at least onevalue may be independently selected regardless of whether the UCI istransmitted via PUSCH with data or not. The at least one value may beP_(O) _(_) _(PUSCH,f,c)(j_(SPCSI)) and/or α_(f,c)(j_(SPCSI)). Thewireless device may determine an uplink transmit power based on the atleast one value, for example, if the UCI is transmitted with data (e.g.,UL SCH data) via a PUSCH (e.g., piggybacking on the PUSCH). The wirelessdevice may determine an uplink transmit power based on the at least onevalue, for example, if the UCI is transmitted without data (e.g., UL SCHdata) via a PUSCH.

A wireless device may determine whether at least one value of an uplinktransmit power component for SP CSI on a PUSCH is used, depending onwhether the UCI is transmitted with data or not, for example, if a UCIcomprising at least one SP CSI report is transmitted via a PUSCH (e.g.,piggyback on the PUSCH). The at least one value may be at least one ofP_(O) _(_) _(PUSCH,f,c)(j) and/or α_(f,c)(j) (e.g., P_(O) _(_)_(PUSCH,f,c)(j_(SPCSI)), and/or α_(f,c)(j_(SPCSI))). The at least onevalue may be semi-statically configured for a transmission of a UCIwithout data (e.g., UL SCH data) via a PUSCH. The number of bits in theUCI may be small, for example, in comparison with the number of bits inUL SCH data. The transmission of the UCI without data may need a larger(or smaller) transmit power, for example, if the uplink transmit powerdepends on the number of bits to be transmitted. The at least one value(e.g., P_(O) _(_) _(PUSCH,f,c)(j_(SPCSI)) and/or α_(f,c)(j_(SPCSI))) maybe used to increase (or decrease) transmit power for the transmission ofthe UCI without data.

The at least one SP CSI report may be transmitted without data via aPUSCH, for example, after or in response to receiving a DCI indicatingan activation of at least one SP CSI setting associated with the atleast one SP CSI report. The wireless device may transmit the at leastone SP CSI report without data via a PUSCH, for example, if there is nouplink grant scheduled with the transmission of the at least one SP CSI.The wireless device may determine uplink transmit power based on atleast one value of uplink transmit power components semi-staticallyconfigured (or predefined) for SP CSI. The wireless device may selectP_(O) _(_) _(PUSCH,f,c)(j_(SPCSI)) and/or α_(f,c)(j_(SPCSI)) for P_(O)_(_) _(PUSCH,f,c)(j) and/or α_(f,c)(j) in the uplink transmit power(e.g., P_(PUSCH,f,c)(i, j, q_(d), l) of the transmission of UCI via aPUSCH on a carrier f of a cell c. A wireless device may determine thePUSCH transmission power P_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) in aPUSCH transmission period i as

${P_{{PUSCH},f,c}\left( {i,j_{SPCSI},q_{d},l} \right)} = {\min \begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\; \_ \; {PUSCH}},f,c}\left( j_{SPCSI} \right)} + {10{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},f,c}^{PUSCH}(i)}} \right)}} +} \\{{{\alpha_{f,c}\left( j_{SPCSI} \right)} \cdot {{PL}_{f,c}\left( q_{d} \right)}} + {\Delta_{{TF},f,c}(i)} + {f_{f,c}\left( {i,l} \right)}}\end{Bmatrix}}$

[dBm] (where j_(SPCSI)∈{0,1,2, . . . , J−1}=S_(J)), for example, if thewireless device transmits at least one SP CSI via a PUSCH on the carrierf of the cell c using SP CSI parameter set configuration with indexj_(SPCSI) and PUSCH power control adjustment state with index l.

The at least one SP CSI report may be transmitted with data via a PUSCH.The at least one SP CSI report may be transmitted, for example, after orin response to receiving a DCI indicating an activation of at least oneSP CSI setting associated with the at least one SP CSI report. The atleast one SP CSI report may be transmitted, for example, after or inresponse to receiving a MAC CE indicating an activation of at least oneSP CSI setting. The wireless device may transmit the at least one SP CSIreport with data via a PUSCH, for example, if the at least one SP CSIreport (e.g., scheduled to transmit via a PUSCH or PUCCH) is piggybackedon a PUSCH with a data transmission. The wireless device may determineuplink transmit power based on at least one value of uplink transmitpower components semi-statically configured (or predefined) for the datatransmission. The wireless device may select P_(O) _(_)_(PUSCH,f,c)(j_(data)) and/or α_(f,c)(j_(data)) for P_(O) _(_)_(PUSCH,f,c)(j) and/or α_(f,c)(j) in the uplink transmit power (e.g.,P_(PUSCH,f,c)(i, j, q_(d), l)) of the transmission of a UCI via a PUSCHon a carrier f of a cell c. A wireless device may determine the PUSCHtransmission power P_(PUSCH,f,c)(i, j_(data), q_(d), l) in PUSCHtransmission period i as

${P_{{PUSCH},f,c}\left( {i,j_{data},q_{d},l} \right)} = {\min \begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\; \_ \; {PUSCH}},f,c}\left( j_{data} \right)} + {10{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},f,c}^{PUSCH}(i)}} \right)}} +} \\{{{\alpha_{f,c}\left( j_{data} \right)} \cdot {{PL}_{f,c}\left( q_{d} \right)}} + {\Delta_{{TF},f,c}(i)} + {f_{f,c}\left( {i,l} \right)}}\end{Bmatrix}}$

[dBm] (where j_(data)∈{0,1,2, . . . , J−1}=S_(J)), for example, if thewireless device transmits at least one SP CSI via a PUSCH (e.g.,piggybacked on the PUSCH) on a carrier f of a cell c using parameter setconfiguration with index j_(data) and PUSCH power control adjustmentstate with index l.

FIG. 35A shows an example of uplink transmit power that is based on oneor more values associated with SP CSI. FIG. 35B shows an example ofuplink transmit power that is based on one or more values associatedwith data (e.g., UL SCH data). In FIG. 35A and FIG. 35B, a UCIcomprising at least one SP CSI may be piggybacked (e.g., multiplexed) ona PUSCH carrying UL SCH data.

A wireless device may receive, from a base station, at least one messagecomprising at least one of: at least one first parameter to determine afirst power value; at least one second parameter to determine a secondpower value; a third parameter indicating a first allowed power valuefor a cell; and/or at least one second parameter indicating at least oneconfiguration parameter of at least one SP CSI report. The wirelessdevice may receive one or more first DCIs indicating an activation ofone or more transmissions of the at least one SP CSI report, via a PUSCHof the cell. The one or more transmissions may comprise a first SP CSItransmission in a first time occupancy of the PUSCH of the cell. Thewireless device may determine a first transmission power of the first SPCSI transmission in the first time occupancy of the PUSCH. The firsttransmission power may be based on a first target received power, forexample, if a second transmission of at least one transport block (TB)in a second time occupancy of the PUSCH of the cell is overlapped withat least a portion of the first time occupancy. The first transmissionpower may be based on a second target received power, for example, if noTB is transmitted in a second time occupancy of the PUSCH that isoverlapping with at least a portion of the first time occupancy of thePUSCH. The wireless device may transmit the first SP CSI based on thefirst transmission power. The first power value may indicate the firsttarget received power. The first power value may indicate the secondtarget received power. The overlapped portion in time axis may be atleast one OFDM symbol. The overlapped portion in time axis may be atleast a portion of one OFDM symbol. The overlapped portion (e.g., intime axis) may be at least one slot (e.g., mini-slot, or subframe). Theoverlapped portion (e.g., in time axis) may be at least a portion of oneslot (e.g., mini-slot, or subframe).

A base station (e.g., a gNB) may configure a wireless device (e.g., aUE) with at least one SP CSI setting and may transmit a DCI scrambled byan RNTI for SP CSI (e.g., SP CSI RNTI), or a MAC CE, that indicates anactivation of at least one SP CSI setting (e.g., activation of SP CSIreporting). The wireless device may transmit a first UCI comprising atleast one SP CSI report in a first time occupancy of the physicalchannel (TTI, slot, mini-slot, or subframe) via a PUSCH or PUCCH. The atleast one SP CSI is associated with the at least one SP CSI setting. Thefirst UCI may be transmitted via a PUSCH, for example, if the at leastone SP CSI setting is activated by a DCI. The first UCI may betransmitted via a PUCCH, for example, if the at least one SP CSI settingis activated by a MAC CE.

The wireless device may transmit the first UCI, via a PUSCH, withoutdata (e.g. UL-SCH data), for example, if there is no uplink grant forthe PUSCH in a second time occupancy of the physical channel (TTI, slot,mini-slot, or subframe). The first time occupancy scheduled to carry atleast one SP CSI report may not be overlapped in at least a firstportion of the second time occupancy, the first time occupancy may notstart within a first time interval after the scheduled termination ofthe second time occupancy, or the second time occupancy may not startwithin a first time interval after the scheduled termination of thefirst time occupancy.

The wireless device may transmit the first UCI with data (e.g. UL-SCHdata), for example, if the wireless device has the data with an uplinkgrant (e.g., dynamic, configured, and/or semi-persistent grant) totransmit via a PUSCH in a third time occupancy of the physical channel(TTI, slot, mini-slot, or subframe). The first time occupancy may beoverlapped in at least a first portion of the third time occupancy, thefirst time occupancy may start within a first time interval after thescheduled termination of the third time occupancy, or the third timeoccupancy may start within the first time interval after the scheduledtermination of the first time occupancy. The first portion and/or thefirst time interval may be predefined, for example, in terms of severalmicroseconds or milliseconds, at least one OFDM symbol, one or more OFDMsymbols, a portion of one OFDM symbol, and/or one or more TTIs (e.g.,slots, mini-slot, or subframe).

A wireless device may transmit, via a PUSCH, a UCI in parallel with data(e.g., UL SCH). The UCI may comprise at least one SP CSI report. Thewireless device may receive a DCI that indicates an activation of atleast one SP CSI setting. The wireless device may transmit at least oneSP CSI report associated with the at least one SP CSI setting via a timeoccupancy of PUSCH indicated by the at least one SP CSI setting, forexample, after or in response to receiving the DCI.

The wireless device may not suffer from a performance loss, for example,if the UCI is transmitted with data in parallel. The performance lossmay be associated with, for example, peak-to-average power (PAPR) ratio,inter-modulation distortion (IMD), out-of-band (OOB) leakage, and/orreduction in power capability (cubic metric (CM) problem). The wirelessdevice may transmit the UCI with a waveform robust to the performanceloss. For example, the waveform may be DFT spread OFDM, Filter BackMulti Carrier, Generalized FDM, Universally Filtered OFDM, FilteredOFDM, Single Carrier OFDM, and/or CP-OFDM. The wireless device may havefiltering and/or windowing process for the waveform, for example, toreduce the performance loss.

The wireless device may determine the PUSCH transmission powerP_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) for SP CSI and the PUSCHtransmission power P_(PUSCH,f,c)(i, j_(data), q_(d), l) for data inPUSCH transmission period i as

${{P_{{PUSCH},f,c}\left( {i,j_{SPCSI},q_{d},l} \right)} = {\min {\begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\; \_ \; {PUSCH}},f,c}\left( j_{SPCSI} \right)} + {10{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},f,c}^{PUSCH}(i)}} \right)}} +} \\{{{\alpha_{f,c}\left( j_{SPCSI} \right)} \cdot {{PL}_{f,c}\left( q_{d} \right)}} + {\Delta_{{TF},f,c}(i)} + {f_{f,c}\left( {i,l} \right)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}},\mspace{20mu} {and}$${P_{{PUSCH},f,c}\left( {i,j_{data},q_{d},l} \right)} = {\min \begin{Bmatrix}{{P_{{CMAX},f,c}(i)},} \\{{P_{{O\; \_ \; {PUSCH}},f,c}\left( j_{data} \right)} + {10{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},f,c}^{PUSCH}(i)}} \right)}} +} \\{{{\alpha_{f,c}\left( j_{data} \right)} \cdot {{PL}_{f,c}\left( q_{d} \right)}} + {\Delta_{{TF},f,c}(i)} + {f_{f,c}\left( {i,l} \right)}}\end{Bmatrix}}$

[dBm], respectively, (where j_(SPCSI), j_(data)∈{0,1,2, . . . ,J−1}=S_(J) and j_(data)≠j_(SPCSI)), for example, if the wireless devicetransmits a UCI comprising at least one SP CSI and data in parallel viaa PUSCH, on a carrier f of a cell c using SP CSI parameter setconfiguration with index j_(SPCSI), data transmission parameter setconfiguration with index j_(data) and PUSCH power control adjustmentstate with index l. P_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) andP_(PUSCH,f,c)(i, j_(data), q_(d), l) may be P_(PUSCH,f,c)(i, j_(SPCSI),q_(d), l)=P_(O) _(_) _(PUSCH,f,c)(j_(SPCSI))+10 log₁₀(2^(μ)·M_(RB,f,c)^(PUSCH)(i))+α_(f,c)(j_(SPCSI))·PL_(f,c)(q_(d))+Δ_(TF,f,c)(i)+(i, l)[dBm], and P_(PUSCH,f,c)(i, j_(data), q_(d), l)=P_(O) _(_)_(PUSCH,f,c)(j_(data))±10 log₁₀(2^(μ)·M_(RB,f,c)^(PUSCH)(i))+α_(f,c)(j_(data))·PL_(f,c)(q_(d))+Δ_(TF,f,c)(i)+f_(f,c)(i,l)[dBm], respectively, where j_(SPCSI), j_(data)∈{0,1,2, . . . ,J−1}=S_(J) and j_(data)≠j_(SPCSI).

The wireless device may determine a PUSCH transmission power required totransmit the UCI and data, for example, if the wireless device transmitsa UCI comprising at least one SP CSI and data in parallel via the PUSCH.The total PUSCH transmission power may comprise P_(PUSCH,f,c)(i,j_(SPCSI), q_(d), l) and P_(PUSCH,f,c)(i, j_(data), q_(d), l). The totalPUSCH transmission power may be a sum of linear values ofP_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) and P_(PUSCH,f,c)(i, j_(data),q_(d), l) (e.g., a sum of {circumflex over (P)}_(PUSCH,f,c)(i,j_(SPCSI), q_(d), l) and {circumflex over (P)}_(PUSCH,f,c)(i, j_(data),q_(d), l)). The wireless device may adjust (scale up or down, change,(re)calculate, or (re)determine) the total PUSCH transmission power suchthat the total PUSCH transmission power is smaller than the allowedpower value, for example, if the total PUSCH transmission power exceeds(or higher than or equal to) an allowed power value on a carrier f ofthe cell c (e.g., P_(CMAX,f,c)(i) and/or a linear value ofP_(CMAX,f,c)(i) ({circumflex over (P)}_(CMAX,f,c)(i))). The wirelessdevice may adjust (e.g., scale) {circumflex over (P)}_(PUSCH,f,c)(i,j_(SPCSI), q_(d), l) with a first scaling value and {circumflex over(P)}_(PUSCH,f,c)(i, j_(data), q_(d),l) with a second scaling value. Thefirst and second scaling values may be predefined and/or semi-staticallyconfigured. The first scaling value may be equal to the second scalingvalue. The wireless device may adjust (e.g., scale) {circumflex over(P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) and {circumflex over(P)}_(PUSCH,f,c)(i, j_(data), q_(d), l) such that Σ_(j∈{j) _(SPCSI)_(,j) _(data) _(})ω_(j){circumflex over (P)}_(PUSCH,f,c)(i, j, q_(d),i)≤{circumflex over (P)}_(CMAX,f,c)(i), where 0≤ω_(j)≤1 is a scalingvalue for index j.

FIG. 36 shows an example of the total PUSCH transmission power adjusting(e.g., scaling down) in a cell. A threshold 3630 shown in FIG. 36 may bethe allowed power value configured with a wireless device for the cell.The wireless device may successfully transmit SP CSI and UL SCH data,for example, if the wireless device adjusts (e.g., scales down) thetotal PUSCH transmission power 3610 to a reduced total PUSCHtransmission power 3620. The adjusting (e.g., scaling) of total PUSCHtransmission power may not affect the reception of the PUSCH at a basestation, for example, if a difference between the total PUSCHtransmission power and the allowed power value (e.g., a threshold 3630)is small. The parallel transmission of control data (e.g., SP CSIreport) and data (e.g., UL SCH data) may be beneficial, for example, ifthe difference between the total PUSCH transmission power and theallowed power value is small. The wireless device may drop one ofcontrol data (e.g., SP CSI report) and data (e.g., UL SCH data), forexample, if the total PUSCH transmission power is higher than theallowed power value. The wireless device and the base station may needto schedule the one of control data (e.g., SP CSI report) and data(e.g., UL SCH data), which may cause a longer latency. It may reduce thelatency, for example, if the wireless device transmits SP CSI and UL SCHdata in parallel.

The wireless device may receive, from a base station, at least onemessage comprising at least one of: a first parameter indicating a firstallowed power value for a cell and/or at least one second parameterindicating at least one configuration parameter of at least one SP CSIreport. The wireless device may receive one or more first DCIsindicating an activation of transmissions of the at least one SP CSIreport, via a PUSCH of the cell. The transmissions comprise a first SPCSI transmission in a first time occupancy of the PUSCH. The wirelessdevice may receive one or more second DCIs indicating an uplink radioresource assignment for a second transmission of at least one TB, viathe PUSCH of the cell, in a second time occupancy of the PUSCH. Thesecond time occupancy may at least partially overlap with the first timeoccupancy in time axis. The wireless device may determine a firsttransmission power of the first SP CSI transmission in the first timeoccupancy and a second transmission power of the second transmission.The wireless device may adjust (e.g., scale down, change, etc.) atransmission power of a sum of the first transmission and the secondtransmission to be lower than the first allowed power value. Thewireless device may transmit, with the transmission power, the at leastone SP CSI report in the first time occupancy and the at least one TB inthe second time occupancy. At least a portion of the at least one SP CSIreport transmission may overlap with at least a portion of the at leastone TB transmission. The transmission overlap may be at least one OFDMsymbol in time axis. The transmission overlap may be at least one slotin time axis. The transmission overlap may be at least one subframe intime axis.

The base station may fail to detect and/or decode the control data (e.g.SP CSI) and data (e.g., UL SCH data), for example, if the wirelessdevice scale down the total PUSCH transmission power to adjust the totalPUSCH transmission power value to be lower than the allowed power value.The scaled total PUSCH transmission power may not allocate enoughtransmit power to the control data and/or data, for example, if adifference between the total PUSCH transmission power and the allowedpower value is greater than a threshold. Insufficient transmit power mayresult in detection and/or decoding failure at the base station. Theinsufficient transmit power may cause the base station to request one ormore retransmissions that may cause a longer latency (delay). Thewireless device may have first data (e.g., control data and/or URLLCdata) that may require high reliability and low latency. Scaling downthe total PUSCH transmission power may not be desirable, for example, ifthe wireless device schedules to transmit the first data.

A wireless device may drop and/or scale down at least one first PUSCHtransmission to adjust the total PUSCH transmission power to be lowerthan the allowed power value, for example, if total PUSCH transmissionpower exceeds the allowed power value of a cell. The dropping and/orscaling down the at least one first PUSCH transmission may provideflexibility in DL and/or UL scheduling (e.g., the base station and thewireless device may schedule one or more data packets depending on itsrequirements), for example, if total PUSCH transmission power exceedsthe allowed power value. The dropping and/or scaling down the at leastone first PUSCH transmission may satisfy one or more servicerequirements (reliability, and/or latency) for at least one second PUSCHtransmission. The at least one second PUSCH transmission may be datatransmission requiring high reliability and/or low latency (e.g., URLLCdata transmission). The at least one second PUSCH transmission may becontrol data (e.g., periodic/aperiodic, and/or SP CSI) transmission thatmay be associated with scheduling of one or more subsequenttransmissions and/or DL/UL interference management. The at least onefirst PUSCH transmission is for a CSI report, for example, if thewireless device transmits the CSI report periodically. The dropping ofone CSI report may not significantly degrade the network performanceand/or aperiodic CSI and/or SP CSI may compensate the loss of the oneCSI report, for example, if the base station is configured to receivethe CSI report periodically.

The wireless device may prioritize the one or more PUSCH transmissions,for example, overlapped in at least a portion of time in a cell and maydrop (and/or scale a power of) at least one of the one or more PUSCHtransmissions based on the priorities of the one or more PUSCHtransmissions, for example, if the wireless device have one or morePUSCH transmissions to be transmitted in parallel to a base station viathe cell. The wireless device may drop (and/or scale power of) at leastone first PUSCH transmission of the one or more PUSCH transmission, forexample, if the total PUSCH transmission power for transmitting the oneor more PUSCH transmissions exceeds the allowed power value of the cell.The at least one first PUSCH transmission may have a lower priority thanat least one second PUSCH transmission of the one or more PUSCHtransmission. The wireless device may drop (and/or scale a power of) theat least one second PUSCH transmission, for example, if the total PUSCHtransmission power before the dropping (and/or scaling down a power of)the at least one first PUSCH transmission exceeds the allowed powervalue. The wireless device may continue to drop (and/or scale down powerof) at least one of the one or more PUSCH transmissions based on thepriorities until the adjusted total PUSCH transmission power is lowerthan (or equal to) the allowed power value.

The data (e.g., UL SCH data) transmission may have a higher prioritythan the SP CSI transmission. The data may carry URLLC traffic that mayrequire low latency. The wireless device may drop the SP CSItransmission, for example, after or in response to determining that thetotal PUSCH transmission power of a cell is higher than the allowedpower value of the cell (e.g., {circumflex over (P)}_(CMAX,f,c)(i)) andthat the data transmission is prioritized over the SP CSI transmission.The wireless device may drop the SP CSI transmission scheduled on aPUSCH, for example, if the total PUSCH transmission power is higher thanthe allowed power value. {circumflex over (P)}_(PUSCH,f,c)(i, j_(data),q_(d), l) may be higher than the allowed power value or {circumflex over(P)}_(PUSCH,f,c)(i, j_(data), q_(d), l) may be lower than the allowedpower value. The wireless device may drop the SP CSI transmissionscheduled on a PUSCH, for example, if the PUSCH transmission power fordata, {circumflex over (P)}_(PUSCH,f,c)(i, j_(data), q_(d), l), islarger (or higher) than the allowed power value. The wireless device mayscale down {circumflex over (P)}_(PUSCH,f,c)(i, j_(data), q_(d), l) suchthat {circumflex over (P)}_(PUSCH,f,c)(i, j_(data), q_(d), l) is lowerthan the allowed power value, for example, after or in response todropping the SP CSI transmission.

FIG. 37A shows an example of power allocation based on determining thatthe PUSCH transmission power for data is higher than the allowed powervalue. For example, the PUSCH transmission power 3710A for UL SCH datais higher than the allowed power value (e.g., a threshold 3730A). ThePUSCH transmission power 3710A for UL SCH data may be scaled down to thetotal PUSCH transmission power 3720A. The scheduled SP CSI transmissionmay be dropped. For example, the SP CSI transmission power 3740A may bescaled down to zero and be dropped.

FIG. 37B shows an example of power allocation based on determining thatthe PUSCH transmission power for data is lower than the allowed powervalue. For example, the PUSCH transmission power 3710B for UL SCH datais lower than the allowed power value (e.g., a threshold 3730B). ThePUSCH transmission power 3710B for UL SCH data may not be scaled down.The scheduled SP CSI transmission may be dropped. For example, the SPCSI transmission power 3740B may be scaled down to zero and be dropped.The PUSCH transmission power 3710B may be the total PUSCH transmissionpower 3720B after the power allocation.

The wireless device may use {circumflex over (P)}_(PUSCH,f,c)(i,j_(SPCSI), q_(d), l) and/or {circumflex over (P)}_(PUSCH,f,c)(i,j_(data), q_(d), l) adjusted by the power allocation, for example, forat least the parallel (or simultaneous) transmissions of the SP CSI andthe PUSCH data during at least one of the overlapped portion, the firsttime occupancy, and/or the second time occupancy.

The wireless device may receive, from a base station, at least onemessage comprising at least one of: a first parameter indicating a firstallowed power value for a cell and/or at least one second parameterindicating at least one configuration parameter of at least one SP CSIreport. The wireless device may receive one or more first DCIsindicating an activation of transmissions of the at least one SP CSIreport, via a PUSCH of the cell. The transmissions may comprise a firstSP CSI transmission in a first time occupancy of the PUSCH. The wirelessdevice may receive one or more second DCIs indicating an uplink radioresource assignment for a second transmission of at least one transportblock (TB), via the PUSCH of the cell, in a second time occupancy of thePUSCH. The second time occupancy may overlap with the first timeoccupancy in at least a portion. The wireless device may determine afirst transmission power of the first SP CSI transmission in the firsttime occupancy and a second transmission power of the secondtransmission. The wireless device may drop the first transmission, forexample, after or in response to determining that the secondtransmission power exceeding the first allowed power value. The wirelessdevice may scale down transmission power of the second transmissionpower to be lower than the first allowed power value. The wirelessdevice may transmit, with the adjusted transmission power, the at leastone TB at least in the overlapped portion and/or the second timeoccupancy. The overlapped portion may be at least one OFDM symbol intime axis. The overlapped portion may be at least one slot in time axis.The overlapped portion may be at least one subframe in time axis.

The wireless device may receive, from a base station, at least onemessage comprising at least one of: a first parameter indicating a firstallowed power value for a cell and/or at least one second parameterindicating at least one configuration parameter of at least one SP CSIreport. The wireless device may receive one or more first DCIsindicating an activation of transmissions of the at least one SP CSIreport, via a PUSCH of the cell. The transmissions may comprise a firstSP CSI transmission in a first time occupancy of the PUSCH. The wirelessdevice may receive one or more second DCIs indicating an uplink radioresource assignment for a second transmission of at least one transportblock (TB), via the PUSCH of the cell, in a second time occupancy of thePUSCH. The second time occupancy may overlap with the first timeoccupancy in at least a portion. The wireless device may determine afirst transmission power of the first SP CSI transmission in the firsttime occupancy and a second transmission power of the secondtransmission. The wireless device may drop the first transmission, forexample, after or in response to determining that a sum of the firsttransmission power and the second transmission power exceeds the firstallowed power value. The second transmission power may be lower than thefirst allowed power value. The wireless device may transmit, with thesecond transmission power, the at least one TB at least in theoverlapped portion and/or the first time occupancy. The overlappedportion may be at least one OFDM symbol in time axis. The overlappedportion may be at least one slot in time axis. The overlapped portionmay be at least one subframe in time axis.

The data (e.g., UL SCH data) transmission may have a higher prioritythan the SP CSI transmission. The data may carry URLLC traffic that mayrequire low latency. The wireless device may scale down (or up) thePUSCH transmission power for SP CSI, for example, after or in responseto determining that the total PUSCH transmission power is higher thanthe allowed power value (e.g., {circumflex over (P)}_(CMAX,f,c)(i)) andthat the data transmission is prioritized over the SP CSI transmission.The wireless device may scale up or down the PUSCH transmission powerfor SP CSI such that the total PUSCH transmission power is smaller thanthe allowed power value, for example, if the PUSCH transmission powerfor data, {circumflex over (P)}_(PUSCH,f,c)(i, j_(data), q_(d), l), issmaller (or lower) than the allowed power value.

FIG. 38 shows an example of power allocation in a cell. The wirelessdevice may use {circumflex over (P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l)and/or {circumflex over (P)}_(PUSCH,f,c)(i, j_(data), q_(d), l) adjustedby the power allocation during at least overlapped portion, the firsttime occupancy, and/or the second time occupancy. The wireless devicemay determine that a sum of UL SCH data transmission power 3810 and SPCSI transmission power 3840 exceeds an allowed power value (e.g., athreshold 3830). The wireless device may determine that the UL SCH datatransmission is prioritized over the SP CSI transmission. The wirelessdevice may determine that the UL SCH data transmission power 3810 doesnot exceed the allowed power value. The wireless device may determine toscale down the SP CSI transmission power 3840 to the reduced SP CSItransmission power 3850, for example, based on a difference between theallowed power value and the UL SCH data transmission power 3810. Thewireless device may determine the reduced SP CSI transmission power 3850such that the allowed power value is greater than or equal to totalPUSCH transmission power 3820 (e.g., a sum of the reduced SP CSItransmission power 3850 and the UL SCH data transmission power 3810).The wireless device may transmit, to the cell (or to a base station viathe cell), at least one SP CSI report using {circumflex over(P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) and data using P_(PUSCH,f,c)(i,j_(data), q_(d), l) during at least overlapped portion.

The wireless device may receive, from a base station, at least onemessage comprising at least one of: a first parameter indicating a firstallowed power value for a cell and/or at least one second parameterindicating at least one configuration parameter of at least one SP CSIreport. The wireless device may receive one or more first DCIsindicating an activation of transmissions of the at least one SP CSIreport, via a PUSCH of the cell. The transmissions may comprise a firstSP CSI transmission in a first time occupancy of the PUSCH. The wirelessdevice may receive one or more second DCIs indicating an uplink radioresource assignment for a second transmission of at least one transportblock (TB), via the PUSCH of the cell, in a second time occupancy of thePUSCH. The second time occupancy may overlap with the first timeoccupancy in at least a portion. The wireless device may determine afirst transmission power of the first SP CSI transmission in the firsttime occupancy and a second transmission power of the secondtransmission. The wireless device may scale down a transmission power ofthe first transmission power, for example, after or in response todetermining that a sum of the first transmission power and the secondtransmission power exceeds the first allowed power value. The secondtransmission power may be lower than the first allowed power value. Thewireless device may transmit the at least one SP CSI report, based onthe first transmission power, at least in the overlapped portion and/orthe first time occupancy. The wireless device may transmit the at leastone TB based on the transmission power at least in the overlappedportion and/or the second time occupancy. The transmission power may belower than the first allowed power value. The overlapped portion may beat least one OFDM symbol (e.g., in time axis). The overlapped portionmay be at least one slot in time axis. The portion may be at least onesubframe (e.g., in time axis).

The data (e.g., UL SCH data) transmission may have a lower priority thanthe SP CSI transmission. For example, a downlink and/or uplinkscheduling may depend on the control data (e.g., SP CSI) that thewireless device transmits. Unsuccessful reception and/or detection ofthe control data may negatively affect the downlink and/or uplinkscheduling (e.g., longer latency). The wireless device may drop the datatransmission, for example, after or in response to determining that thetotal PUSCH transmission power is higher than the allowed power value(e.g., {circumflex over (P)}_(CMAX,f,c)(i)), and that the SP CSItransmission is prioritized over the data transmission. The wirelessdevice may drop the data transmission scheduled on a PUSCH, for example,if the total PUSCH transmission power is higher than the allowed powervalue. {circumflex over (P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) may behigher than the allowed power value or {circumflex over(P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) may be lower than the allowedpower value. The wireless device may drop the data transmissionscheduled on PUSCH, for example, if the PUSCH transmission power for SPCSI, {circumflex over (P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l), islarger (or higher) than the allowed power value. The wireless device mayscale down {circumflex over (P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l)such that {circumflex over (P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) islower than the allowed power value, for example, based on or in responseto determining to drop the data transmission.

FIG. 39A shows an example of power allocation based on determining thatthe PUSCH transmission power for SP CSI is higher than the allowed powervalue. For example, the SP CSI transmission power 3910A is higher thanthe allowed power value (e.g., a threshold 3930A) of a cell. The SP CSItransmission power 3910A may be scaled down to the total PUSCHtransmission power 3920A of the cell. The PUSCH transmission 3940Ascheduled on the cell for UL SCH data may be dropped. For example, thePUSCH transmission power 3940A scheduled on the cell for the UL SCH datamay be scaled down to zero and be dropped.

FIG. 39B shows an example of power allocation based on determining thatthe PUSCH transmission power for SP CSI is lower than the allowed powervalue of a cell. For example, the SP CSI transmission power 3910B may belower than the allowed power value (e.g., a threshold 3930B) of thecell. The SP CSI transmission power 3910B may not be scaled down. ThePUSCH transmission scheduled on the cell for UL SCH data may be dropped.For example, the PUSCH transmission power 3940B for the UL SCH data maybe scaled down to zero and be dropped. The SP CSI transmission power3910B may be the total PUSCH transmission power 3920B after the powerallocation.

The wireless device may use {circumflex over (P)}_(PUSCH,f,c)(i,j_(SPCSI), q_(d), l) and/or {circumflex over (P)}_(PUSCH,f,c)(i,j_(data), q_(d), l) adjusted by the power allocation during at least oneof the overlapped portion, the first time occupancy, and/or the secondtime occupancy in time axis.

The wireless device may receive, from a base station, at least onemessage comprising at least one of: a first parameter indicating a firstallowed power value for a cell and/or at least one second parameterindicating at least one configuration parameter of at least one SP CSIreport. The wireless device may receive one or more first DCIsindicating an activation of transmissions of the at least one SP CSIreport, via a PUSCH of the cell. The transmissions may comprise a firstSP CSI transmission in a first time occupancy of the PUSCH. The wirelessdevice may receive one or more second DCIs indicating an uplink radioresource assignment for a second transmission of at least one transportblock (TB), via the PUSCH of the cell, in a second time occupancy of thePUSCH. The second time occupancy may overlap with the first timeoccupancy in at least a portion. The wireless device may determine afirst transmission power of the first SP CSI transmission in the firsttime occupancy and second transmission power of the second transmission.The wireless device may drop the second transmission, for example, basedon or in response to determining that the first transmission powerexceeds the first allowed power value. The wireless device may scaledown transmission power of the first transmission power to be lower thanthe first allowed power value. The wireless device may transmit, withthe transmission power, the at least one SP CSI report at least in theoverlapped portion and/or the first time occupancy. The overlappedportion may be at least one OFDM symbol in time axis. The overlappedportion may be at least one slot in time axis. The overlapped portionmay be at least one subframe in time axis.

The wireless device may drop the second transmission, for example, basedon or in response to determining that a sum of the first transmissionpower and the second transmission power exceeds the first allowed powervalue. The first transmission power may be lower than the first allowedpower value. The wireless device may transmit, to the cell and with thefirst transmission power, the at least one SP CSI report at least in theoverlapped portion and/or the first time occupancy.

The data (e.g., UL SCH data) transmission may have a lower priority thanthe SP CSI transmission. A downlink and/or uplink scheduling may dependon the control data (e.g., SP CSI) that the wireless device transmits.The unsuccessful reception and/or detection of the control data maynegatively affect the downlink and/or uplink scheduling (e.g., longerlatency). The wireless device may scale down (or up) the PUSCHtransmission power for data, for example, based on or in response todetermining that the total PUSCH transmission power is higher than theallowed power value (e.g., {circumflex over (P)}_(CMAX,f,c)(i)) and thatthe SP CSI transmission is prioritized over the data transmission. Thewireless device may scale up or down the PUSCH transmission power for SPCSI such that the total PUSCH transmission power is smaller than theallowed power value, for example, if the PUSCH transmission power for SPCSI, {circumflex over (P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l), issmaller (or lower) than the allowed power value.

FIG. 40 shows an example of power allocation. The wireless device mayuse {circumflex over (P)}_(PUSCH,f,c)(i, j_(SPCSI), q_(d), l) and/or{circumflex over (P)}_(PUSCH,f,c)(i, j_(data), q_(d), l) adjusted by thepower allocation during at least one of the overlapped portion, thefirst time occupancy, and/or the second time occupancy.

The wireless device may receive, from a base station, at least onemessage comprising at least one of: a first parameter indicating a firstallowed power value for a cell and/or at least one second parameterindicating at least one configuration parameter of at least one SP-CSIreport. The wireless device may receive one or more first DCIsindicating an activation of transmissions of the at least one SP CSIreport, via a PUSCH of the cell. The transmissions may comprise a firstSP CSI transmission in a first time occupancy of the PUSCH. The wirelessdevice may receive one or more second DCIs indicating an uplink radioresource assignment for a second transmission of at least one TB, viathe PUSCH of the cell, in a second time occupancy of the PUSCH. Thesecond time occupancy may overlap with the first time occupancy in atleast a portion. The wireless device may determine a first transmissionpower of the first SP CSI transmission in the first time occupancy andsecond transmission power of the second transmission. The wirelessdevice may scale down the transmission power of the second transmissionpower, for example, based on or in response to determining that a sum ofthe first transmission power and the second transmission power exceedsthe first allowed power value. The first transmission power may be lowerthan the first allowed power value. The wireless device may transmit theat least one SP CSI report based on the first transmission power atleast in the overlapped portion and/or the first time occupancy. Thewireless device may transmit the at least one TB based on thetransmission power at least in the overlapped portion and/or the secondtime occupancy. The transmission power may be lower than the firstallowed power value. The overlapped portion may be at least one OFDMsymbol in time axis. The portion may be at least one slot in time axis.The overlapped portion may be at least one subframe (e.g., in timeaxis).

FIG. 41 shows an example of an uplink grant procedure that may beperformed by a base station. At step 4102, the base station maytransmit, to a wireless device, a DCI activating one or more SP CSIreports for a cell. For the activation of SP CSI (e.g., activation of SPCSI reporting) for a wireless device, the base station may determine oneor more uplink resources of the cell for receiving the one or more SPCSI reports. For example, the base station may indicate one or morePUSCH channels in one or more time/frequency resources of the cell inwhich the one or more SP CSI reports can be included.

At step 4104, the base station may receive, from the wireless device, arequest for an uplink grant that grants a transmission of one or moreTBs. For example, the wireless device may determine to transmit the oneor more TBs (e.g., UL SCH data) to the base station (e.g., via the cell)and generate the request for the uplink grant that may indicate theamount of data of the one or more TBs. The base station may determineone or more PUSCH resources in which the wireless device may transmitthe one or more TBs.

At step 4106, the base station may determine whether the base station isable to decode the received SP CSI and the one or more TBs that areoverlapped in time. The base station may determine whether the wirelessdevice is able to transmit, to the cell, the SP CSI and the one or moreTBs simultaneously. If yes, the base station may perform step 4108. Ifno, the base station may perform step 4110.

At step 4108, the base station may transmit, to the wireless device, asecond DCI comprising an uplink grant that indicates one or moreresources overlapping with SP CSI transmission resource(s) in a PUSCH ofa cell. The base station may transmit, to the wireless device, one ormore power control parameters such that the wireless device maydetermine priority between the SP CSI transmission to the cell and theTB transmission to the cell, determine whether to scale downtransmission power of at least one of the SP CSI transmission and the TBtransmission, and/or determine whether to drop at least one of the SPCSI transmission and the TB transmission. At step 4110, the base stationmay transmit, to the wireless device, a second DCI comprising an uplinkgrant for a cell that indicates one or more resources not overlappingwith SP CSI transmission resource(s) of the cell. The transmission powerfor each of the SP CSI transmission and the TB transmission may bedetermined based on an allowed power value for an uplink transmission(e.g., {circumflex over (P)}_(CMAX,f,c)(i)), for example, if the one ormore resources for the TB transmission does not overlap with SP CSItransmission resource(s) in a PUSCH of a cell.

FIG. 42 shows an example of an uplink power control procedure that maybe performed by a wireless device. At step 4202, the wireless device maydetermine at least one uplink data (e.g., one or more TB s, UL SCH data,etc.) transmission is scheduled. The wireless device may determine,based on an uplink grant received from a base station, one or moreuplink resources for the at least one uplink data transmission. At step4204, the wireless device may determine whether the SP CSI transmissionand the uplink data transmission are overlapped in time. At step 4206,the wireless device may perform the scheduled transmissions, forexample, if the SP CSI transmission and the uplink data transmission arenot overlapped in time.

At step 4208, the wireless device may determine whether totaltransmission power for the parallel transmissions to a cell exceeds athreshold, for example, if the SP CSI transmission and the uplink datatransmission are overlapped in time. The wireless device may performstep 4206, for example, if the total transmission power for the paralleltransmissions to the cell does not exceed the threshold. At step 4210,the wireless device may determine whether the required power for theuplink data transmission exceeds the threshold, for example, if thetotal transmission power for the parallel transmissions to the cellexceeds the threshold. At step 4212, the wireless device may scale downthe required power for the SP CSI transmission such that the changedtotal transmission power of the SP CSI and uplink data transmissions islower than the threshold, for example, if the required power for theuplink data transmission to the cell does not exceed the threshold.

At step 4214, the wireless device may drop the SP CSI transmission, forexample, if the required power for the uplink data transmission to thecell exceeds the threshold. At step 4216, the wireless device may scaledown the transmission power for the uplink data transmission to the cellsuch that the changed transmission power for the uplink datatransmission to the cell is lower than the threshold. The wirelessdevice may perform the transmissions of the SP CSI and the uplink dataafter step 4216.

A base station may send, to a wireless device, at least one messageindicating an allowed power value for a cell. For example, the at leastone message (e.g., at least one RRC message) may comprise one or morepower control parameters (e.g., uplink power control parameters). Afirst power control parameter may indicate the allowed power value. Theat least one message may comprise a first RNTI and a second RNTI. The atleast one message may comprise configuration parameters associated withone or more SP CSI reports. The configuration parameters may comprise areporting configuration of the one or more SP CSI reports and a resourceconfiguration of the one or more SP CSI reports. The base station maysend, to the wireless device, a first control message (e.g., a DCI or aMAC CE) indicating an activation of one or more SP CSI reports (e.g.,activation of SP CSI reporting). The first control message may bescrambled based on the first RNTI. The wireless device may validate, atleast based on a first field (e.g., an HARQ process number field) and asecond field (e.g., a redundancy version field) in a DCI of the firstcontrol message, a message format that indicates the activation. Thewireless device may validate the message format based on the first fieldindicating a first value and the second field indicating a second value.The first value and/or the second value may be predefined (e.g., in thebase station and/or the wireless device). A first transmission of theone or more SP CSI reports may be scheduled for an uplink resource(e.g., an uplink carrier, an uplink channel, etc.) of the cell. The basestation may send, to the wireless device, a second control message(e.g., a PDCCH comprising a DCI) indicating an uplink grant of a secondtransmission for the uplink resource. The second control message may bescrambled based on the second RNTI. The uplink resource may comprise oneor more uplink shared channel (e.g., PUSCH) resources, of the cell, forwhich the first transmission and the second transmission are scheduled.The wireless device may determine, based on one or more configurationparameters of the at least one message, one or more uplink channelresources comprising the uplink resource. The wireless device mayschedule, based on the one or more uplink channel resources, the firsttransmission for the uplink resource. The wireless device may schedule,based on the uplink grant, the second transmission for the uplinkresource. The first transmission may at least partially overlap in timewith the second transmission. The overlapped portion may comprise aperiod of time (e.g., at least one OFDM symbol, at least one slot,etc.). The wireless device may determine a combined transmission powercomprising a first transmission power of the first transmission and asecond transmission power of the second transmission, for example, basedon the one or more power control parameters. The wireless device mayadjust (e.g., drop or scale down) one or more of the first transmissionpower or the second transmission power. The adjusting may be at leastbased on the combined transmission power (e.g., a sum of the firsttransmission power and the second transmission power) exceeding theallowed power value. The adjusting may be based on determining that thefirst transmission at least partially overlaps in time with the secondtransmission. The adjusting may be at least based on determining thatthe second transmission power is less than the allowed power value. Thewireless device may drop the first transmission, for example, if thewireless device determines that the second transmission power exceedsthe allowed power value. The wireless device may scale down the firsttransmission power, for example, if the wireless device determines thatthe second transmission power is less than the allowed power value. Thewireless device may send, via the uplink resource and during a timeperiod in which the first transmission at least partially overlaps intime with the second transmission, at least one of the one or more SPCSI reports using the adjusted first transmission power and at least onetransport block using the second transmission power. A sum of theadjusted first transmission power and the second transmission power maybe less than or equal to the allowed power value. The base station maysend, to the wireless device, a third control message (e.g., a DCI or aMAC CE) indicating a deactivation of one or more SP CSI reports (e.g.,deactivation of SP CSI reporting). The wireless device may validate,based on a plurality of fields of the third control message, a messageformat that indicates the deactivation.

A base station may send, to a wireless device, at least one message. Theat least one message may comprise power control parameters comprising anallowed power value for a cell. The at least one message may compriseconfiguration parameters associated with one or more SP CSI reports. Thebase station may send, to the wireless device, a first control messageindicating an activation of one or more SP CSI reports (e.g., activationof SP CSI reporting). The wireless device may determine, based on atleast one of the configuration parameters and the first control message,a first uplink resource for a first transmission of at least one of theone or more SP CSI reports. The wireless device may determine, based onan uplink grant, a second uplink resource for a second transmission of atransport block. The wireless device may adjust one or more of: a firsttransmission power of the first transmission or a second transmissionpower of the second transmission. The adjusting may be at least based ona combined transmission power, comprising the first transmission powerand the second transmission power, exceeding the allowed power value.The adjusting may be at least based on a time proximity between thefirst uplink resource and the second uplink resource. The wirelessdevice may send, via at least a portion of the second uplink resourceand based on the adjusting, one or more of: the transport block, or theat least one of the one or more SP CSI reports. The wireless device mayadjust the first transmission power, for example, if the wireless devicedetermines that the second transmission power is less than the allowedpower value. The wireless device may drop the first transmission andadjust the second transmission power, for example, if the wirelessdevice determines that the second transmission power exceeds the allowedpower value.

FIG. 43 shows general hardware elements that may be used to implementany of the various computing devices discussed herein, including, forexample, the base station 401, the wireless device 406, or any otherbase station, wireless device, or computing device described herein. Thecomputing device 4300 may include one or more processors 4301, which mayexecute instructions stored in the random access memory (RAM) 4303, theremovable media 4304 (such as a Universal Serial Bus (USB) drive,compact disk (CD) or digital versatile disk (DVD), or floppy diskdrive), or any other desired storage medium. Instructions may also bestored in an attached (or internal) hard drive 4305. The computingdevice 4300 may also include a security processor (not shown), which mayexecute instructions of one or more computer programs to monitor theprocesses executing on the processor 4301 and any process that requestsaccess to any hardware and/or software components of the computingdevice 4300 (e.g., ROM 4302, RAM 4303, the removable media 4304, thehard drive 4305, the device controller 4307, a network interface 4309, aGPS 4311, a Bluetooth interface 4312, a WiFi interface 4313, etc.). Thecomputing device 4300 may include one or more output devices, such asthe display 4306 (e.g., a screen, a display device, a monitor, atelevision, etc.), and may include one or more output device controllers4307, such as a video processor. There may also be one or more userinput devices 4308, such as a remote control, keyboard, mouse, touchscreen, microphone, etc. The computing device 4300 may also include oneor more network interfaces, such as a network interface 4309, which maybe a wired interface, a wireless interface, or a combination of the two.The network interface 4309 may provide an interface for the computingdevice 4300 to communicate with a network 4310 (e.g., a RAN, or anyother network). The network interface 4309 may include a modem (e.g., acable modem), and the external network 4310 may include communicationlinks, an external network, an in-home network, a provider's wireless,coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., aDOCSIS network), or any other desired network. Additionally, thecomputing device 4300 may include a location-detecting device, such as aglobal positioning system (GPS) microprocessor 4311, which may beconfigured to receive and process global positioning signals anddetermine, with possible assistance from an external server and antenna,a geographic position of the computing device 4300.

The example in FIG. 43 is a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 4300 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 4301, ROM storage 4302, display 4306, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 43.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

One or more features of the disclosure may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a UE, a base station, and the like) toenable operation of multi-carrier communications described herein. Thedevice, or one or more devices such as in a system, may include one ormore processors, memory, interfaces, and/or the like. Other examples maycomprise communication networks comprising devices such as basestations, wireless devices or user equipment (UE), servers, switches,antennas, and/or the like. A network may comprise any wirelesstechnology, including but not limited to, cellular, wireless, WiFi, 4G,5G, any generation of 3GPP or other cellular standard or recommendation,wireless local area networks, wireless personal area networks, wirelessad hoc networks, wireless metropolitan area networks, wireless wide areanetworks, global area networks, space networks, and any other networkusing wireless communications. Any device (e.g., a wireless device, abase station, or any other device) or combination of devices may be usedto perform any combination of one or more of steps described herein,including, for example, any complementary step or steps of one or moreof the above steps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the disclosure. Accordingly, theforegoing description is by way of example only, and is not limiting.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice from a base station, at least one message comprising one or moreuplink power control parameters associated with an uplink transmission;receiving a control message indicating an activation of one or moresemi-persistent channel state information (SP CSI) reports; determininga transmission power for a transmission of at least one of the one ormore SP CSI reports, wherein the transmission power is based on: the oneor more uplink power control parameters; and at least one correctionvalue adjusted based on the activation; and transmitting, via an uplinkchannel and based on the transmission power, the at least one of the oneor more SP CSI reports.
 2. The method of claim 1, wherein the controlmessage comprises a medium access control control element (MAC CE)indicating the activation.
 3. The method of claim 1, wherein the controlmessage comprises a first field indicating a logical channel identifierthat indicates whether the control message is used to activate ordeactivate one or more SP CSI reports.
 4. The method of claim 3, whereinthe control message comprises a second field indicating whether thecontrol message indicates the activation.
 5. The method of claim 1,further comprising: receiving a second control message indicating adeactivation of one or more SP CSI reports; and adjusting, based onreceiving the second control message, the at least one correction valueto a different value.
 6. The method of claim 5, further comprising:scheduling a second transmission of uplink information, wherein thesecond transmission is after receiving the second control message;determining, based on the at least one correction value being adjustedto the different value, a second transmission power for the secondtransmission; and transmitting, based on the second transmission power,the uplink information.
 7. The method of claim 1, further comprising;receiving a radio network temporary identifier associated with the oneor more SP CSI reports; and determining, based on the radio networktemporary identifier and downlink control information of the controlmessage, an indication of the activation.
 8. The method of claim 7,further comprising validating, based on a plurality of fields in thedownlink control information, the activation.
 9. A method comprising:receiving, by a wireless device from a base station, at least onemessage comprising one or more uplink power control parametersassociated with an uplink transmission; transmitting, by the wirelessdevice and to the base station, one or more semi-persistent channelstate information (SP CSI) reports; receiving a control messageindicating a deactivation of one or more SP CSI reports; determining atransmission power for a transmission of uplink information, wherein thetransmission power is based on: the one or more uplink power controlparameters; and at least one correction value adjusted based on thedeactivation; and transmitting, based on the transmission power andafter receiving the control message, the uplink information.
 10. Themethod of claim 9, further comprising: receiving a second controlmessage indicating an activation of one or more SP CSI reports;determining a second transmission power for a transmission of at leastone of the one or more SP CSI reports, wherein the second transmissionpower is based on: the one or more uplink power control parameters; andthe at least one correction value adjusted based on the activation,wherein transmitting the one or more SP CSI reports comprisestransmitting, based on the second transmission power, the at least oneof the one or more SP CSI reports.
 11. The method of claim 9, furthercomprising receiving a first medium access control control element (MACCE) indicating an activation of one or more SP CSI reports, and whereinthe control message comprises a second MAC CE indicating thedeactivation.
 12. The method of claim 9, wherein the control messagecomprises a first field indicating a logical channel identifier thatindicates whether the control message is used to activate or deactivateone or more SP CSI reports, and wherein the control message comprises asecond field indicating whether the control message indicates thedeactivation.
 13. The method of claim 9, further comprising: setting,based on an activation of one or more SP CSI reports, the at least onecorrection value to a first value, and setting, based on thedeactivation, the at least one correction value to a second value. 14.The method of claim 13, wherein the first value equals the second value.15. The method of claim 9, further comprising; receiving a radio networktemporary identifier associated with the one or more SP CSI reports; anddetermining, based on the radio network temporary identifier anddownlink control information of the control message, an indication ofthe deactivation.
 16. A method comprising: receiving, by a wirelessdevice and from a base station, at least one control message comprisingat least one of: a first indication of activating one or moresemi-persistent channel state information (SP CSI) reports; or a secondindication of deactivating one or more SP CSI reports; adjusting, basedon at least one of the first indication or the second indication, atleast one correction value associated with a transmission power of atransmission of uplink information; determining, based on the adjustedat least one correction value, the transmission power; and transmitting,via an uplink channel and based on the transmission power, the uplinkinformation.
 17. The method of claim 16, wherein the uplink informationcomprises one or more of: the one or more SP CSI reports; or one or moreuplink shared channel data.
 18. The method of claim 16, wherein the atleast one control message comprises a first field indicating a logicalchannel identifier that indicates whether the control message is used toactivate or deactivate one or more SP CSI reports, and wherein the atleast one control message comprises a second field indicating whetherthe control message indicates the activating of the one or more SP CSIreports.
 19. The method of claim 16, further comprising: receiving aradio network temporary identifier associated with the one or more SPCSI reports; and determining, based on the radio network temporaryidentifier and downlink control information of the at least one controlmessage, the first indication or the second indication.
 20. The methodof claim 16, wherein adjusting the at least one correction valuecomprises: setting, based on the first indication, the at least onecorrection value to a first value, and setting, based on the secondindication, the at least one correction value to a second value.